🚧Refactor function parameter names

[CalvinWilkinson]

Complete The Item Below

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

Description

Refactor parameter names for various functions in the RepoClient class and sanitize incoming relative file paths:
This is to make the meaning of the parameters more clear, which in turn improves the API.

Do the following:

1. Rename the branchName parameter to ref for the following functions in the RepoClient:
   • getFileContent
   • fileExists
   • getFileContentInternal
2. Update the code docs for the parameters.
3. Sanitize the relativeFilePath parameters by trimming any ., /, \, and ~ characters from the beginning of the paths.
   This ensures that using these common characters for paths does not cause issues with the URL's construction during the concatenation of the URL and the relative file path. Also, make sure that the URL's owner/repo/contents section and the relative file path are separated by a / character.
4. Remove the check of absolute file paths from the functions. Refer to the check below.

Acceptance Criteria

The items to complete to satisfy the Definition of Done.

Preview Give feedback

1. All the unit tests have been executed and passed locally after the PR work is complete. (Why? Refer to 'Additional Information' below.)
2. Function param names refactored
3. Incoming relative path sanitized
4. The isAbsolute() check removed from functions

ToDo Items

The items to complete to satisfy the Definition of Done.

Preview Give feedback

1. Add a change type label to the issue. Refer to the Change Type Labels section below.
2. Add a priority label to the issue. Refer to the Priority Type Labels section below.
3. Link the issue to the correct milestone (if applicable).

Issue Dependencies

No response

Related Work

No response

Additional Information:

Unit Tests

Reasons for local unit test execution:

• Unit tests might pass locally but not in the CI environment during the status check process or vice-versa.
• Tests might pass on the developer's machine but not necessarily on the code reviewer's machine.
• If you notice that the test status check has passed but the test failed locally, please notify a project maintainer!

💡Warning💡
If the unit tests pass remotely and are not executed locally, this means we could be letting a bug slip into production.
Though bugs will always exist in some capacity, we should all do our part to help prevent them from happening.

Change Type Labels

Change Type	Label
Bug Fixes	🐛bug
Breaking Changes	🧨breaking-changes
New Feature	✨new-feature
CICD Changes	♻️cicd
Config Changes	⚙️config
Performance Improvements	🏎️performance
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.

[CalvinWilkinson]

Sanitation of the relative file path was fixed in the bug issue below:

• 🚧Fix bug with file exists function #91