feat: fetch a role in an organisation endpoint

[sparkybug]

Description

Develop an API endpoint to fetch a specific role within an organisation.
​

Related Issue (Link to Github issue)

#418
​

Motivation and Context

Enable users to fetch a specific role within an organisation.
​

How Has This Been Tested?

Unit Tests:

• Successful response with valid organisation ID and role ID.
• Invalid organisation ID format.
• Invalid role ID format.
• Non-existent organisation ID.
• Non-existent role ID.
• Internal server error.
  ​

Screenshots (if appropriate - Postman, etc):

​

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
  ​

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[timiajayi]

need additional approval

[sparkybug]

need additional approval

@Dev-Tonia please help approve this. God bless you!

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13348460	Triggered	Generic High Entropy Secret	20560c6	.env.example	View secret
13348460	Triggered	Generic High Entropy Secret	7c37feb	.env.example	View secret
13348443	Triggered	Generic High Entropy Secret	7e6c24b	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	7e6c24b	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	20560c6	tests/Unit/RegistrationTest.php	View secret
13348443	Triggered	Generic High Entropy Secret	20560c6	tests/Unit/RegistrationTest.php	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[timiajayi]

failing test

[timiajayi]

Merge conflict

[timiajayi]

Merge conflict

[sparkybug]

Merge conflict

I have fixed this boss.