🚧Create service to get PR branch info

[CalvinWilkinson]

Complete The Item Below

• I have updated the title without removing the 🚧 emoji.

Description

Problem:
Currently, getting pull request branch information will only work by using the GitHubActions.HeadRef or GitHubActions.BaseRef. Using this is only good in the GitHub environment because that is the only time the GitHubActions instance is NOT NULL.
This means that running pull request-related stuff locally becomes an issue because the object instance is null.

Solution:
To allow this functionality to work, create a service that will detect if the build is a server build or a local build. If it is a server build, use the GitHubActions instance, if it is a local build, use the GitHubClient to interact with the API to be able to get the branch information required.

To maximize the testability of the new service, create a thin wrapper around the GitHubActions object that can be injected into the new service for use. This way we are not found to server only state and can easily maximize our testability.

Once the new service is complete, refactor the use cases throughout the code base to use the new service instead of the GitHubActions object.

Acceptance Criteria

• Create service GitRepoService - ✨new feature New feature that does not exist
  • Commit property added
  • Branch property added
• Create service GitHubActions object created - ✨new feature New feature that does not exist
  • Name of service should be GitHubActionsService.
  • Token property added.
  • Actor property added.
    • If on the server, just GitHubActions object. If local, use the currently logged in user name.
  • Ref property added.
  • BaseRef property added.
    • Needs to be nullable as well as explain with code docs that it is only used on the server.
  • HeadRef property added.
    • If on the server, use the GitHubActions.HeadRef. If local, use the current branch.
  • PullRequestNumber property added.
    • Needs to be nullable as well as explain with code docs that it is only used on the server.
  • Refactor code throughout the code base to use the new service instead of the raw GitHubActions object.

ToDo Items

• Change type labels added to this issue. Refer to the Change Type Labels section below.
• Priority label added to this issue. Refer to the Priority Type Labels section below.
• Issue linked to the correct project (if applicable).
• Issue linked to the correct milestone (if applicable).
• Draft pull request created and linked to this issue (only required with code changes).

Issue Dependencies

No response

Related Work

No response

Additional Information:

Change Type Labels

Change Type	Label
Bug Fixes	🐛bug
Breaking Changes	🧨breaking changes
New Feature	✨new feature
Workflow Changes	workflow
Code Doc Changes	🗒️documentation/code
Product Doc Changes	📝documentation/product

Priority Type Labels

Priority Type	Label
Low Priority	low priority
Medium Priority	medium priority
High Priority	high priority

Code of Conduct

• I agree to follow this project's Code of Conduct.