feat(i18n): introduce a new @asgardeo/i18n package

[brionmario]

Purpose

This pull request updates project documentation and issue templates to improve clarity, add support for the new @asgardeo/i18n package, and enhance contributor guidance. The most significant changes are grouped below.

Issue Template Improvements:

• Added @asgardeo/i18n and other as selectable areas in bug, improvement, and new feature templates to reflect new package support and broader categorization. [1] [2] [3]
• Updated labels and descriptions in issue templates for better clarity, including instructions for version fields. [1] [2] [3] [4]
• Removed the legacy issue_template.md file to avoid confusion and redundancy.

Documentation and Contribution Guide Enhancements:

• Significantly revised CONTRIBUTING.md:
  • Updated references from "Web UI SDKs" to "JavaScript SDKs" for accuracy.
  • Improved formatting and consolidated recommended development tools into a table for easier reading.
  • Expanded and clarified commit message guidelines, including new scope conventions for all packages and more detailed examples.
  • Added detailed instructions for contributing translations to the @asgardeo/i18n package, including testing and documentation update steps.
  • Clarified documentation contribution process and moved it to the end for better organization. [1] [2]

Repository Maintenance:

• Added .editorconfig and .eslintignore files to the @asgardeo/i18n package to ensure consistent code style and proper linting/ignore rules. [1] [2]

Pull Request Template Update:

• Updated the PR template to clarify checklist items and provide more explicit instructions for contributors.

Related Issues

• Fixes feat: introduce a new @asgardeo/i18n module #178

Related PRs

• N/A

Checklist

• e2e cypress tests locally verified.
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Ran FindSecurityBugs plugin and verified report?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?