Changing adafruit_bus_device to duck typing

[gamblor21]

The first attempt at moving bus device to the core assumed the bus was the busio I2C when it could be bitbangio or others. The new methods use duck typing to call the function names regardless of the underlying bus.

[gamblor21]

Created as a draft for a code review while I continue to test it. I may require help to make sure the changes solve some of the reported issues.

I also wanted to check/ask if anyone sees anything to be done with the SPI portion of the code or is it safer to assume that always will use the SPI bus (in which case I need to check for it and raise an error if not).

I have not yet re-enabled the flag to build it.

[jepler]

Thank you! No testing performed, but I read through the changes and found a couple of items that can use attention.

[gamblor21]

Ready for review. This was done to fix the root cause for these issues:
#3856 - With duck typing this should no longer be an issue. I tested it using busio, bitbangio and a test class that just implemented the basic functions expected from the duck typing (and otherwise did nothing)
#3821 - I do not have a SHTC3 sensor to test this with. But the new code exactly copies the python code

I only have a couple I2C devices I can test with. So far most of my testing was with the BME280. I will dig out the others I have to keep going.

There is one build also failing and I am unsure why.

[jepler]

This looks very much like I expect. No testing performed.

[jepler]

The lone build failure was an occasional CI weirdness.

[gamblor21]

In addition to the BME280 tested with PCT2075, BH1750 and BNO-055 with busio.I2C and bitbangio.I2C. All work except the BNO-055 with bitbangio, but testing it with the python busdevice library the issue persisted so seems to be an issue with that library or bitbangio and not with this build.