chore: update repo structure

[brionmario]

Purpose

This pull request introduces several new configurations and updates to the project to enhance development workflows, code quality, and release processes. Key changes include the addition of changeset configurations, editor and linter configurations, GitHub workflows for pull requests and releases, and the removal of outdated configurations.

Configuration and Workflow Enhancements:

• .changeset/config.json: Added configuration for changesets to manage versioning and publishing.
• .github/workflows/pr-builder.yml: Introduced a GitHub Actions workflow to build and test pull requests, including linting, type checking, and unit testing.
• .github/workflows/release.yml: Added a GitHub Actions workflow to automate the release process, including creating release pull requests and publishing to npm.

Code Quality and Editor Configurations:

• .editorconfig: Added editor configuration to standardize coding styles across different editors and IDEs.
• .eslintrc.js: Introduced ESLint configuration to enforce coding standards and integrate with Prettier for consistent code formatting.
• .eslintignore and .prettierignore: Added ignore files to exclude specific directories and files from linting and formatting.

Cleanup and Removal of Legacy Configurations:

• .travis.yml and .jshintrc: Removed legacy Travis CI configuration and JSHint configuration as they are no longer needed. [1] [2]

Related Issues

• Initialize the repository as a mono-repo, enforce best practices & prepare for the first release 🎉 #4

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 ESLint & Prettier plugins and verified?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?