drivers: rename ads101x driver to ads1x1x

[baptleduc]

Contribution description

This PR renames the existing ads101x driver to ads1x1x.
The purpose of this change is to prepare the codebase and to simplify the review process for supporting both the ADS101x and ADS111x families in a unified driver.

No functional changes are introduced in this PR.
Only file names, Kconfig symbols, defines macros, and related references have been updated to reflect the new driver name.

This rename will simplify the review process for upcoming PR that extend the driver to handle the ADS111x family.

Testing procedure

Build and run existing tests/drivers/ads1x1x (now renamed accordingly) to confirm no regressions.

Issues/PRs references

A follow-up PR will introduce ADS111x support and internal handling of family-specific differences.

[riot-ci]

Murdock results

✔️ PASSED

3fcc23a drivers/ads101x: rename doxygen excludes

Success	Failures	Total	Runtime
10516	0	10516	14m:04s

Artifacts

• Documentation preview

[baptleduc]

The macro defines weren’t documented before I renamed them, which caused the CI to fail after the renaming.
What I don’t understand is how the CI passed before, since it shouldn’t have.

[leandrolanzieri]

The failure seems to be related to moving the Kconfig file:

kconfiglib.KconfigError: /tmp/dwq.0.1912543697952842/44aa831c8a8590889923f0e364609cb7/drivers/Kconfig:32: '/tmp/dwq.0.1912543697952842/44aa831c8a8590889923f0e364609cb7/drivers/ads101x/Kconfig' not found (in 'rsource "ads101x/Kconfig"'). Check that environment variables are set correctly (e.g. $srctree, which is unset or blank). Also note that unset environment variables expand to the empty string.

You probably need to also update this line:

RIOT/drivers/Kconfig

Line 32 in db7a67b

rsource "ads101x/Kconfig"

[baptleduc]

Ok it passed Murdock CI. But the static tests always failed because I didn't touch the documentation during the renaming process, and it was missing from the start.

[baptleduc]

So do I need to comment the macros for the review ?

[maribu]

The alternative to adding Doxygen comments documenting the macros would be to update the list of expected Doxygen errors. That list will contain exceptions for the old file, but is missing them for the new file.