Add extended I2C HAL functions

[agarof]

What's new

• Add two functions furi_hal_i2c_tx_ext and furi_hal_i2c_rx_ext, giving the user more flexibility in writing I2C drivers by giving them more choices such as sending RESTART conditions and using multiple buffers in the same transaction.
• Enable transfers larger than 255 bytes by automatically using the reload flag, The flag has been added to existing functions and shouldn't be an API breaking change.
• Make the timeout for multi-transactions functions such as furi_hal_i2c_trx shared between all transactions instead of being duplicated.
• Fix an issue where we wait for the timeout to expire when a device is not present on the bus in both the RX/TX functions and furi_hal_i2c_is_device_ready.
• Add ten bit addresses support (untested).

I tried to keep the binary size increase to a minimum but this still adds about 300 bytes to the final binary (304 in debug, 296 in compact).

Verification

To check for basic functionality, simply boot the Flipper. Non working code will cause the communication with the battery control chips and the LED driver to fail, resulting in missing battery readouts and no screen backlight.
More advanced verification must be done using a logic analyzer.
As I have not opened my Flipper, I have only checked the behavior using the external bus.

Checklist (For Reviewer)

• PR has description of feature/bug or link to Confluence/Jira task
• Description contains actions to verify feature/bugfix
• I've built this code, uploaded it to the device and verified feature/bugfix

[agarof]

This could be simplified, since both values are equal, depending on how close to ST's LL you want to stick.

[skotopes]

We'd rather hide anything related to ST LL inside.

[skotopes]

Unit tests needed: can be gauge, charger or led driver.

[skotopes]

un draft when ready

[agarof]

I have fixed the functions and enums naming and have checked that the furi_hal (LED driver communication) and power (charger) tests pass.

[skotopes]

I've pushed bunch of small edits: docs update, const qualifier usage cleanup, fix with incorrect argument pass. In general everything looks good.

We do need one last thing: unit tests, they must cover newly added features.
You can use any of existing flipper chips or some other popular one that we can buy and add to our unit tests stand.

[agarof]

I have added two unit tests, one testing the Restart and Pause / Resume features, the other testing the auto-reload feature.

The first uses the LED driver, same as the existing tests.
The second uses an I2C EEPROM connected to the external bus. It writes 512 bytes 16 at a time then reads them all at once, so the EEPROM needs to be at least 512 bytes large and have a 16 bytes page write buffer. Most I2C EEPROMs I have found, such as these two, match these characteristics and have the same addressing scheme as the one I have (I don't have a reference for it).

[skotopes]

That was some great work, you did well ;-)