CIP-1694 | Update French version to Commit (89bb166)

[Hornan7]

• Change old hydra ledger spec links to GitHub repo (CIP-1694 correction | Fix ledger spec links #548 ) (Commit baa4ad5)
• Removed rationale TOC link "Treasury withdrawals vs Project Catalyst" (CIP-1694 correction | Fix Rationale TOC for undefined Catalyst item #547) (Commit 89bb166)

[rphair]

@Hornan7 here we have a problem common with new GitHub users on the Developer Portal and CIP repos, which is seen when commits from your previous PR(s) also show up in a new PR (like above), which spoils the configuration management.

This is mainly because you have been working on the master branch of your own fork, instead of properly creating a new branch just for these changes, and also because you haven't synced your fork with the upstream cardano-foundation repository.

There is no way of fixing these problems through this PR, so it has to be closed. Please take these steps before opening a new PR with your changes:

1. First sync your own GitHub fork with its upstream repository. Then your own fork will have the older commits above already merged into it, forming a new baseline upon which your newer changes will be made. See: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

2. If you follow the instructions at this link completely, the master branch in the fork on your own computer will also have the latest upstream changes... e.g. the local file with English version will have these links updated and the obsolete link removed. Don't proceed until you verify this: get some general help on git and GitHub if not.

3. Create a local branch where you can do your edits, since as you can see above it's impossible to continue working from master. Example branch name: cip-1694fr-fix-links. See: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches

4. When you've committed your changes, submit your pull request from that branch.

Other GitHub help links in the sidebar will detail all the steps of this process if & when you get stuck. When you've done the process correctly, the PR that you submit will only have the new commits for the new changes you've made in your new branch. 🤓