feat: add issue configuration and CI checks

[daniellacosse]

This pull request introduces several improvements, including new GitHub issue templates, updated documentation, automated quality checks, and the addition of license headers to multiple files. These changes aim to streamline issue reporting, enhance build instructions, ensure code quality, and comply with licensing requirements.

GitHub Issue Templates and Configuration:

• Added a new bug report template (.github/ISSUE_TEMPLATE/bug_report.yml) to guide users in reporting issues, including steps to reproduce and environment details.
• Added a feature request template (.github/ISSUE_TEMPLATE/feature_request.yml) to help users propose new features with detailed descriptions and use cases.
• Updated the GitHub issue configuration to include a contact link for the community's Reddit page (.github/ISSUE_TEMPLATE/config.yml).

Documentation Updates:

• Revised README.md to swap the iOS and Android build instructions, providing updated dependencies and clearer steps for building Android and iOS apps. [1] [2] [3]
• Removed the "commonly occurring issues" section from README.md, which was previously marked as a TODO.

Automation and Quality Checks:

• Introduced a new GitHub Actions workflow (.github/workflows/quality_checks.yml) to automate quality checks, including Android and iOS builds and license header validation.
• Added a .vscode/settings.json file to associate the YAML schema for GitHub issue configuration with the corresponding file.

Licensing Compliance:

• Added Apache 2.0 license headers to various source files and templates across the project, ensuring compliance with licensing requirements. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

---

Note

Punting lint to a separate PR. GTS lints TS files with no way to properly configure it for MJS files: google/gts#655
We likely want to remove go and convert the existing files to TS before adding the Google-standard GTS linter.

Closes #5

[jyyi1]

Thanks! This will be useful!

[jyyi1]

Thanks. LGTM.