docs: update relative issue paths in CONTRIBUTING.md (#1128)

* docs: update relative issue paths

This commit fixes references to the GitHub's issues page.

CONTRIBUTING.md

@@ -48,14 +48,14 @@ By participating, you are expected to uphold this code. Please report unacceptab
 ## I Have a Question
 
 > [!TIP]
-> If you want to ask a question, we assume that you have read the available [Documentation](https://docs.haystack.deepset.ai/v2.0/docs/intro).
+> If you want to ask a question, we assume that you have read the available [documentation](https://docs.haystack.deepset.ai/docs/intro).
 
-Before you ask a question, it is best to search for existing [Issues](/issues) that might help you. In case you have
+Before you ask a question, it is best to search for existing [issues](/../../issues) that might help you. In case you have
 found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to
 search the internet for answers first.
 
 If you then still feel the need to ask a question and need clarification, you can use one of our
-[Community Channels](https://haystack.deepset.ai/community), Discord in particular is often very helpful.
+[community channels](https://haystack.deepset.ai/community). Discord in particular is often very helpful.
 
 ## Reporting Bugs
 
@@ -67,8 +67,8 @@ investigate carefully, collect information and describe the issue in detail in y
 following steps in advance to help us fix any potential bug as fast as possible.
 
 - Make sure that you are using the latest version.
-- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://docs.haystack.deepset.ai/v2.0/docs/intro). If you are looking for support, you might want to check [this section](#i-have-a-question)).
-- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](/issues).
+- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://docs.haystack.deepset.ai/docs/intro). If you are looking for support, you might want to check [this section](#i-have-a-question)).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](/../../issues?labels=bug).
 - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
 - Collect information about the bug:
   - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
@@ -85,7 +85,7 @@ following steps in advance to help us fix any potential bug as fast as possible.
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
-- Open an [Issue of type Bug Report](/issues/new?assignees=&labels=bug&projects=&template=bug_report.md&title=).
+- Open an [issue of type Bug Report](/../../issues/new?assignees=&labels=bug&projects=&template=bug_report.md&title=).
 - Explain the behavior you would expect and the actual behavior.
 - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
 - Provide the information you collected in the previous section.
@@ -94,7 +94,7 @@ Once it's filed:
 
 - The project team will label the issue accordingly.
 - A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps.
-- If the team is able to reproduce the issue, the issue will scheduled for a fix, or left to be [implemented by someone](#your-first-code-contribution).
+- If the team can reproduce the issue, it will either be scheduled for a fix or made available for [community contribution](#contribute-code).
 
 
 ## Suggesting Enhancements
@@ -106,14 +106,14 @@ to existing ones. Following these guidelines will help maintainers and the commu
 ### Before Submitting an Enhancement
 
 - Make sure that you are using the latest version.
-- Read the [documentation](https://docs.haystack.deepset.ai/v2.0/docs/intro) carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Read the [documentation](https://docs.haystack.deepset.ai/docs/intro) carefully and find out if the functionality is already covered, maybe by an individual configuration.
+- Perform a [search](/../../issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing and distributing the integration on your own.
 
 
 ### How Do I Submit a Good Enhancement Suggestion?
 
-Enhancement suggestions are tracked as GitHub issues of type [Feature request for existing integrations](/issues/new?assignees=&labels=feature+request&projects=&template=feature-request-for-existing-integrations.md&title=).
+Enhancement suggestions are tracked as GitHub issues of type [Feature request for existing integrations](/../../issues/new?assignees=&labels=feature+request&projects=&template=feature-request-for-existing-integrations.md&title=).
 
 - Use a **clear and descriptive title** for the issue to identify the suggestion.
 - Fill the issue following the template
@@ -129,8 +129,8 @@ Enhancement suggestions are tracked as GitHub issues of type [Feature request fo
 If this is your first contribution, a good starting point is looking for an open issue that's marked with the label
 ["good first issue"](https://github.com/deepset-ai/haystack-core-integrations/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22).
 The core contributors periodically mark certain issues as good for first-time contributors. Those issues are usually
-limited in scope, easy fixable and low priority, so there is absolutely no reason why you should not try fixing them,
-it's a good excuse to start looking into the project and a safe space for experimenting failure: if you don't get the
+limited in scope, easy fixable and low priority, so there is absolutely no reason why you should not try fixing them.
+It's also a good excuse to start looking into the project and a safe space for experimenting failure: if you don't get the
 grasp of something, pick another one!
 
 ### Setting up your development environment
@@ -279,7 +279,7 @@ The Python API docs detail the source code: classes, functions, and parameters t
 This type of documentation is extracted from the source code itself, and contributors should pay attention when they
 change the code to also change relevant comments and docstrings. This type of documentation is mostly useful to
 developers, but it can be handy for users at times. You can browse it on the dedicated section in the
-[documentation website](https://docs.haystack.deepset.ai/v2.0/reference/integrations-chroma).
+[documentation website](https://docs.haystack.deepset.ai/reference/integrations-chroma).
 
 We use `pydoc-markdown` to convert docstrings into properly formatted Markdown files, and while the CI takes care of
 generating and publishing the updated documentation at every merge on the `main` branch, you can generate the docs