feat: support highlight in multilayer and subplots

[dakshpokar]

Description

This PR adds support for Highlight in MultiLayer and Subplots in PyMaidr using the newer Maidr TS engine.

Type of Change

• Bug fix
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[Copilot]

Copilot reviewed 24 out of 24 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (2)

maidr/core/enum/maidr_key.py:8

• [nitpick] Since the key was updated from 'selector' to 'selectors' to support multiple values, please update corresponding documentation and ensure that all references in the codebase match the new naming.

SELECTOR = "selectors"

maidr/core/context_manager.py:80

• The switch from contextvars to plain class-level variables for managing elements and selector IDs may introduce thread-safety issues; consider validating that this approach is safe in concurrent environments or document any limitations.

elements = {}

[dakshpokar]

Greetings Professor @jooyoungseo

This project was a formidable challenge, but I'm excited to share our breakthrough. After extensive investigation, collaborative discussions with @SaaiVenkat led us to a pivotal discovery: by refining our implementation of the HighlightContextManager and leveraging matplotlib's internal gid parameter, we can now accurately tag the elements required for highlighting in subplots and multilayer plots. Additionally, this approach has paved the way for implementing the innovative highlight methodology we previously discussed.

Currently, I am using UUIDs to identify elements; however, we have the opportunity to optimize further by tagging SVG elements with specific data points (such as (x, y) coordinates). This enhancement would allow the TS engine to dynamically retrieve these elements without the need for sorting or rearranging, streamlining our process significantly.

Note that this PR is a breaking change and would need TS backend BY DEFAULT!! No backwards compatibility whatsoever.

So finally, I would like to say that this completes the migration to TS engine. I think we are ready to shift the switch to TS by default in Environment. For this we need to merge these PRs in this order -> #153 #154 #155 #156 and finally this PR

Thanks,
Daksh Pokar

[jooyoungseo]

Fantastic! This is a huge enhancement! Thanks a zillion for your hard work, @dakshpokar and @SaaiVenkat !