docs: update hyperlink (#1219)

# [AAP-XXXXX] Brief Title Describing the Change

## Description
<!-- Mandatory: Provide a clear, concise description of the changes and
their purpose -->
- What is being changed?
- Why is this change needed?
- How does this change address the issue?

Closes #XXX (if applicable)
Jira: [AAP-XXXXX](https://jira.aap.com/browse/AAP-XXXXX) (if applicable)

The old link caused `404`, so update it.

## Type of Change
<!-- Mandatory: Check one or more boxes that apply -->
- [ ] 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 not work as expected)
- [x] Documentation update
- [ ] Test update
- [ ] Refactoring (no functional changes)
- [ ] Development environment change
- [ ] Configuration change
- [ ] CI change

## Self-Review Checklist
<!-- These items help ensure quality - they complement our automated CI
checks -->
- [ ] I have performed a self-review of my code
- [ ] I have added relevant comments to complex code sections
- [ ] I have updated documentation where needed
- [ ] I have considered the security impact of these changes
- [ ] I have considered performance implications
- [ ] I have thought about error handling and edge cases
- [ ] I have tested the changes in my local environment
- [ ] I have run the linters and test suite locally
- [ ] I have tested the changes on integration environment

## Testing Instructions
<!-- Optional for test-only changes. Mandatory for all other changes -->
<!-- Must be detailed enough for reviewers to reproduce -->
### Prerequisites
<!-- List any specific setup required -->

### Steps to Test

1.
2.
3.

### Expected Results
<!-- Describe what should happen after following the steps -->

## Additional Context
<!-- Optional but helpful information -->

### Required Actions
<!-- Check if changes require work in other areas -->
<!-- Remove section if no external actions needed -->
- [ ] Requires documentation updates
  <!-- API docs, feature docs, deployment guides -->
- [ ] Requires downstream repository changes
  <!-- Specify repos: django-ansible-base, eda-server, etc. -->
- [ ] Requires infrastructure/deployment changes
  <!-- CI/CD, installer updates, new services -->
- [ ] Requires coordination with other teams
  <!-- UI team, platform services, infrastructure -->
- [ ] Blocked by PR/MR: #XXX |
<https://github.com/example/repo/pull/XXX>
  <!-- Reference blocking PRs/MRs with brief context -->

### Screenshots/Logs
<!-- Add if relevant to demonstrate the changes -->

Signed-off-by: reid_liu <guliu@redhat.com>
Co-authored-by: Alex <aizquier@redhat.com>

Author: reidliu41

docs/contributing.md

@@ -29,7 +29,7 @@ Before you submit a pull request, check that it meets these guidelines:
 1. The pull request should include tests.
 2. The pull request should work for Python 3.11
 3. The pull request should pass all tests, linters and CI checks. You can run
-   each of these locally in your [development environment](docs/development.md)
+   each of these locally in your [development environment](development.md)
 
 ## Communication