Improve the JavaScript lifecycle on repeated attach and correct the core version requirement

Problem/Motivation

Three small robustness problems, all on the repeated-attach path (AJAX, BigPipe, a form rebuild) plus one metadata correction:

• Duplicate DOM ids. js/formatter.js numbers its injected display element from the index of the current attach call. once() only returns containers new to that call, so the index restarts at 0 and a container added later reuses an id already on the page.
• Editors kept forever. js/editor.js keeps every editor in a module-level map and never removes the entry on detach, so destroyed editors stay referenced for the life of the page.
• Core version requirement. ace_editor.info.yml declares ^10, but the code uses str_contains() and other API available from Drupal 10.1, so the declared minimum is lower than what actually runs.

Proposed resolution

• Number the formatter's display elements from a page-wide counter that never repeats.
• Delete the registry entry when an editor is destroyed on detach.
• Declare ^10.1 || ^11 || ^12.

Remaining tasks

• ✅ File an issue
• ✅ Addition/Change/Update/Fix
• ✅ Testing to ensure no regression
• ➖ Automated unit/functional testing coverage
• ➖ Accessibility and Readability
• ❌ Reviewed by a human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ❌ Update Release Notes
• ❌ Release

Release notes snippet

• The formatter no longer reuses element ids when fields are added to a page after the first render, destroyed editors are released, and the module declares Drupal 10.1 as its minimum.