Evaluate PyTango upgrade from 10.1.2 to newer version

Background

We currently have PyTango 10.1.2 installed. The following newer versions are available on PyPI:

Before deciding whether to upgrade, we should answer the following questions.

Questions

Functionality

• Do the newer versions introduce anything useful for our abstraction layer?
• Are there API changes that would make our code simpler or more ergonomic?
• Also keeping in mind LLM (agentic) Usage

Breaking Changes

• Do any versions introduce breaking changes to data structures or interfaces we rely on?
• Is there a migration guide we need to follow?

Dependencies

• Do newer versions require a cppTango upgrade? If so, what is the effort?

Testing

• Do newer versions change behaviour in DeviceTestContext or test utilities that would affect our test suite?
• Do we need to update mocks or fixtures?

Risk

• Is 10.3.0rc1 stable enough to track or pin for future adoption?
• What is the rollback plan if an upgrade breaks something?

References

• news for 1.3.0 release
• 📋 [What's new across versions](https://tango-controls.readthedocs.io/projects/pytango/en/latest/versions/news.html)
• 📖 [Migration guides](https://tango-controls.readthedocs.io/projects/pytango/en/latest/versions/migration/index.html)
• 📦 [PyTango on PyPI](https://pypi.org/project/pytango/#history)
• 🔁 [Full changelog](https://tango-controls.readthedocs.io/projects/pytango/en/latest/versions/revision.html)

Suggested Next Steps

• Read the release notes for 10.1.3, 10.1.4, and 10.3.0rc1
• Assess impact on our codebase and tests
• Decide on upgrade target and timeline

Start with the PyTango 10.1.3, 10.1.4, and 10.3.0rc1 release notes, migration guides, and PyPI history linked in the issue. Inspect the dependency configuration, the abstraction layer, and tests using DeviceTestContext, mocks, or fixtures. Done means documenting compatibility, cppTango requirements, testing impact, upgrade target, and rollback plan.