fix: refactor the src code & add initial ci tests

[jaylenw]

What does this PR do?

The PR makes substantial changes to the src code to resolve the deprecation notices mentioned here https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ and here https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

I expect no API breaking changes. I added testing with Jest and Nock, as well as modified the example GitHub Action Workflows to make sure everything was up to date and all was well. A new GitHub Action workflow has been added to provide coverage reports in PRs.

Documentation has been updated appropriately.

Background info

Resources referenced:

• https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter (Have to use the GITHUB_OUTPUT environment file. The tests explains a lot on how it was done).
• https://dev.to/cicirello/how-to-patch-the-deprecated-set-output-in-github-workflows-and-in-container-actions-9co
• https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
• https://docs.github.com/en/actions/creating-actions/creating-a-composite-action
• https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#get-the-latest-release
• https://stackoverflow.com/questions/63722151/set-github-actions-input-value-for-local-testing (GitHub needs the format of INPUT_{variable-name} available in the system to retrieve it as core.getInput('{variable-name}'), see .jest/setEnvVars.js
• https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#multiline-strings

The node_modules folder has to be committed as documented by GitHub. I have ran npm audit fix to resolve any security vulnerabilities npm found.

You may view the successful workflow runs here https://github.com/CityOfLosAngeles/fetch-latest-github-release/actions/runs/4994739002.

How can this be tested (manually and/or automated test)?

Provide Manual tests Steps if applicable

N/A

Provide steps for running automated tests if applicable

1. Checkout this branch
2. Run npm test

Code coverage report is provided in coverage/.

Which issue(s) is/are related to this PR?

This PR is/are related to issue(s) #6

close #6

[github-actions]

➿ Code coverage

Filename	Statements	Branches	Functions	Lines
action.js	77.55%	63.64%	66.67%	77.55%
config/default.js	100%	100%	100%	100%

[RV-LACity]

@jaylenw , noting that there is a deprecation warning in https://github.com/CityOfLosAngeles/fetch-latest-github-release/actions/runs/4994953857.
Related to use of actions/setup-node@v2, mattallty/jest-github-action@v1 in https://github.com/CityOfLosAngeles/fetch-latest-github-release/blob/ghi-6/.github/workflows/test-coverage.yml

[jaylenw]

@jaylenw , noting that there is a deprecation warning in https://github.com/CityOfLosAngeles/fetch-latest-github-release/actions/runs/4994953857. Related to use of actions/setup-node@v2, mattallty/jest-github-action@v1 in https://github.com/CityOfLosAngeles/fetch-latest-github-release/blob/ghi-6/.github/workflows/test-coverage.yml

Ah yes, I forgot to mention this. I will create an issue for us to explore https://github.com/ArtiomTr/jest-coverage-report-action as it has recent activity suggesting it is maintained. The action I added looks like it is no longer being supported based off of the lack of recent activity. I will create an issue for this and merge this PR for now. Thanks!

[jaylenw]

Noting @RV-LACity Issue created, #8.