kasli_i2c: fix EEPROM access issue in DRTIO networks

[fsagbuya]

ARTIQ Pull Request

Description of Changes

Fix DRTIO EEPROM access for Urukul:

• Add destination parameter to KasliEEPROM to encode DRTIO destination
• Leverage existing remote I2C functionality to access satellite EEPROMs

Test results:
Before:

Writing test values...
Master writing:
305419896
Satellite writing:
-2023406815
Reading values after write:
Master:
-2023406815
Satellite:
-2023406815

After:

Writing test values...
Master writing:
305419896
Satellite writing:
-2023406815
Reading values after write:
Master:
305419896
Satellite:
-2023406815

Related Issue

Closes #2687

Type of Changes

	Type
✓	🐛 Bug fix

Steps (Choose relevant, delete irrelevant before submitting)

All Pull Requests

• Use correct spelling and grammar.
• Update RELEASE_NOTES.rst if there are noteworthy changes, especially if there are changes to existing APIs.
• Close/update issues.
• Check the copyright situation of your changes and sign off your patches (git commit --signoff, see copyright).

Code Changes

• Run flake8 to check code style (follow PEP-8 style). flake8 has issues with parsing Migen/gateware code, ignore as necessary.
• Test your changes or have someone test them. Mention what was tested and how.
• Add and check docstrings and comments
• Check, test, and update the unittests in /artiq/test/ or gateware simulations in /artiq/gateware/test

Git Logistics

• Split your contribution into logically separate changes (git rebase --interactive). Merge/squash/fixup commits that just fix or amend previous commits. Remove unintended changes & cleanup. See tutorial.
• Write short & meaningful commit messages. Review each commit for messages (git show). Format:

  topic: description. < 50 characters total.
  
  Longer description. < 70 characters per line
  

Licensing

See copyright & licensing for more info.
ARTIQ files that do not contain a license header are copyrighted by M-Labs Limited and are licensed under LGPLv3+.

[sbourdeauducq]

Looks dodgy.

[sbourdeauducq]

How does this work?!
The switches obviously need to be set on the satellites instead.

[fsagbuya]

From what I understand, this still works upon testing because remote_i2c automatically sets the switches based on the destination parameter, unlike local_i2c which needs to be set manually.