pico-sdk: Remove unnecessary Kconfig items

[soburi]

• Remove unnecessary Kconfig settings.
• Exclude unnecessary drivers from the build target.
• Remove the include conditions and make all include targets uniform.
• Change claim.c to always be compiled.

These measures will delete unnecessary Kconfig items.

[zephyrbot]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[ajf58]

I'd like to see the first commit message reworded to clarify what's going on. As it's currently written (reading from top to bottom) it reads like this.

1. The Kconfig files were unnecessary, so then I removed them.
2. Then I remove the include conditions and make all include targets uniform.

But this is backwards: because you've made the includes unconditional (and, in some cases also removed some source files from being compiled), the Kconfig options became unnecessary, so could be removed.

This begs the question "is it better to unconditionally have a long list of include directories, or conditionally add them as required?" I prefer the latter, shorter command line calls to the pre-processor, clearer what file it required for what subsystem/driver.

[github-actions]

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud