Convert get-changeset-arguments.sh to TypeScript and add tests

[dskloetc]

Description

When we want to release a single EA or a subset of EAs, we need to pass a list of packages to ignore to yarn changeset version. This list or arguments is computed by .github/scripts/get-changeset-arguments.sh. This script is quite fragile and has needed a number of changes to work around issues. Since there are no tests for it, it's easy to introduce a new bug when fixing a bug.

In this PR we replace the shell script with a Node script and add extensive testing.

The rules to determine the arguments to pass are as follows:

1. Determine which packages to include:
   1. If a package is included, its dependencies have to be included as well (this is a requirement from changeset)
   2. If a package listed in a changeset file is included, other packages listed in the same changeset file have to be included (also a requirement from changeset)
   3. If an included package has changes, packages depending on that package have to be included as well. This is required because we give those depending packages a patch version bump.
2. Determine the list of all packages.
3. Ignore all the packages that should not be included.

Changes

1. Add packages/scripts/src/get-changeset-arguments/index.ts to parse arguments and produce output.
2. Add lib.ts with the core logic.
3. Add repo.ts and realRepo.ts to manage filesystem access and to facilitate injecting repo structures for tests so tests don't start failing when the real repo changes.
4. Add yarn get-changeset-arguments script entry in package.json.
5. Call from yarn get-changeset-arguments instead of .github/scripts/get-changeset-arguments.sh from .github/workflows/upsert-release-pr.yml.
6. Call yarn get-changeset-arguments from .github/scripts/get-changeset-arguments.sh for backwards compatibility (in case it's mentioned in documentation or used in any personal scripts).

Steps to Test

1. Added unit tests.
2. Added fixture.ts to create a temporary repo structure to test real filesystem access.

3. export GITHUB_TOKEN=$(gh auth token)
   yarn changeset version $(.github/scripts/get-changeset-arguments.sh view-function-multi-chain)`
   

Quality Assurance

• If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant infra-k8s configuration file.
• If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant adapter-secrets configuration file.
• If a new adapter was made, or a new endpoint was added, update the test-payload.json file with relevant requests.
• The branch naming follows git flow (feature/x, chore/x, release/x, hotfix/x, fix/x) or is created from Jira.
• This is related to a maximum of one Jira story or GitHub issue.
• Types are safe (avoid TypeScript/TSLint features like any and disable, instead use more specific types).
• All code changes have 100% unit and integration test coverage. If testing is not applicable or too difficult to justify doing, the reasoning should be documented explicitly in the PR.

[changeset-bot]

⚠️ No Changeset found

Latest commit: fb41355

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR