docs: fix: table of contents of contributing md

[JGBSouza]

This PR cleans up the CONTRIBUTING.md file by:

Removing nonexistent sections – the 'Coding Style' and 'Communication' sections have been removed since they are not present in the current document.

Adding the missing License section – a 'License' section has been added to reflect the project’s licensing information.

Updating references – internal links now point to the correct top-level sections instead of the 'Development Workflow' subsection.

These changes improve the accuracy, completeness, and navigability of the CONTRIBUTING.md document.

Closes: #136

[lorenzoberts]

Hey @JGBSouza, thanks for solving this issue. Regarding the changes themselves, all good, ready to merge. My suggestions are related to the commit messages.
Besides what I've said in your previous PR about starting the text with "This commit adds/fixes/changes/etc..", I would also suggest that you use the "docs" prefix even if you're fixing the docs. Instead of "fix: contributing: fix ..." you could use "docs: contributing: fix something in the docs....".
Another thing is that we need the "contributing: " second prefix. Example: "docs: add License section mention to CONTRIBUTING.md". This way i think we are more aligned with conventional commits.

And just to clarify, I could make those changes during merge process, but since you're starting contributing with the project (thanks a lot), it's better that we align this beforehand. For future contributions, if there is a typo or some minor change in the message, don't worry because I'll adjust them by myself.

[JGBSouza]

Hey @JGBSouza, thanks for solving this issue. Regarding the changes themselves, all good, ready to merge. My suggestions are related to the commit messages. Besides what I've said in your previous PR about starting the text with "This commit adds/fixes/changes/etc..", I would also suggest that you use the "docs" prefix even if you're fixing the docs. Instead of "fix: contributing: fix ..." you could use "docs: contributing: fix something in the docs....". Another thing is that we need the "contributing: " second prefix. Example: "docs: add License section mention to CONTRIBUTING.md". This way i think we are more aligned with conventional commits.

And just to clarify, I could make those changes during merge process, but since you're starting contributing with the project (thanks a lot), it's better that we align this beforehand. For future contributions, if there is a typo or some minor change in the message, don't worry because I'll adjust them by myself.

Fixed!

[lorenzoberts]

Thanks @JGBSouza. Merged these commits into the unstable branch. I also just noticed there was a typo in my comment

Another thing is that we need the "contributing: " second prefix. Example: "docs: add License section mention to CONTRIBUTING.md". This way i think we are more aligned with conventional commits.

I meant "is that we don't need the "contributing:" second prefix". Sorry about that, it was misleading. So i fixed the commit message myself, removing the second prefix