Docs: Tweak some links

[louismaximepiton]

Description

Changed some links to blob from current main.

Motivation & Context

Better convey information to people trying to contribute.

Type of changes

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

Checklist

• I have read the contributing guidelines
• My code follows the code style of the project (using npm run lint)
• My change introduces changes to the documentation
• I have updated the documentation accordingly
• (N/A) I have added tests to cover my changes
• All new and existing tests passed

Live previews

• https://deploy-preview-40704--twbs-bootstrap.netlify.app/

Related issues

NA

[julien-deramond]

I was about to approve the PR, but I'm starting to have mixed feelings about it.
I was about to approve the PR, but I'm starting to have mixed feelings about it. On one hand, I like the approach, especially for the contributing guidelines, as it will always link to the latest version, reflecting our current thoughts on how folks should contribute. On the other hand, if the file is moved, all the links in previous versions would need to be updated in gh-pages.

For instance, the CONTRIBUTING.md file could be moved to the root directory or the docs directory, and the package.json could be replaced by another method of managing our repository.

I'll let other core team members share their thoughts, as I still don't have a strong opinion on it.

However, if this PR is not accepted, we should keep the modifications you've made with the backticks ;)

[XhmikosR]

Sorry, don't like that. I'd rather use the variables.