Migrate package to Ember's v2 addon authoring format

[phndiaye]

What does this PR do?

⚠️ This has been generated under control with Codex. The plan is to see how making it tackle the migration as well as all the changes post-codemod + troubleshooting without me doing changes on the side manually can help create a skill + exact step by step instructions for redoing it on other addons (Beside instructions, I only did some git add)

Migrate package to Ember's v2 addon authoring format.

The migration keeps the existing public API surface while modernizing build, package exports, workspace commands, and release tooling.

Key Topics

• Converted the addon to v2 format using @embroider/addon-shim
• Added explicit package exports and resolver-visible app-js mappings for existing services, helpers, modifiers, decorators, and initializers
• Moved runtime build metadata to @embroider/macros via getOwnConfig()
• Simplified the TypeScript build to match the @upfluence/hypermarket pattern:
  • Rollup handles TS sources
  • Babel strips TypeScript syntax
  • @embroider/addon-dev generates declarations
• Removed generated @ijlee2-frontend-configs/* dependencies and config references
• Updated workspace scripts, Makefile targets, pre-push script, and Sonar paths for the new package layout
• Replaced the old manual release script with root-level release-it + workspace plugin configuration

Resources

• https://github.com/ijlee2/ember-codemod-v1-to-v2
• https://medium.com/@phndiaye/migrating-an-ember-addon-to-the-v2-format-1d62e45384d3

🧑‍💻 Developer Heads Up

⚡ Since we are using Ember Octane now:

• Feel free to migrate existing components to Glimmer Components.
• Write new ones exclusively in it.

Useful Resource : Ember Octane vs Classic Cheat Sheet

Good PR checklist

• Title makes sense
• Is against the correct branch
• Only addresses one issue
• Properly assigned
• Added/updated tests
• Added/updated documentation
• Properly labeled