Confirm dependabot version update to issue-trigger.yml

[t-will-gillis]

Prerequisites

1. You must be a member of Hack for LA to work on an issue. If you have not joined yet, please follow the steps on our Getting Started page.
2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Details

NOTE TO REVIEWERS: In order to review this PR, you must create a testing environment on your local repo.

Overview

Our repo's dependabot periodically checks the packages/dependencies used in our codebase to see whether a more recent version is available. When it finds an updated version, the dependabot creates a PR specifying which files will be affected if the package/dependency is updated. We need to check each of these files individually to determine whether we should or should not switch to the latest version.

Action Items

Refer to the issue-trigger.yml file and review the version update(s) recommended by the dependabot.

• Make sure that you have configured your private repo for testing GHAs. See "Details" above.
• Review the expected activity of the GHA, then create a test branch in your local repo to trigger and record the results of the current action.
• Create another test branch to trigger and record the results of the action using the updated package version(s). Change all instances of:

- uses: actions/checkout@v3

to:

- uses: actions/checkout@v4

• Compare results to determine whether the update causes breaking changes, or whether the update causes no apparent change in the expected functioning of the action, and "Approve" or "Request changes" as appropriate.

Resources/Instructions

• Never done GitHub actions? Start here!
• Events that trigger workflows
• Workflow syntax for GitHub Actions
• actions/github-script
• This issue was initiated by Bump actions/checkout from 3 to 4 #5443

[github-actions]

Hi @t-will-gillis, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)