Separate build instructions for Windows and Unix into separate sections in README.md

[mcbarton]

Description

Please include a summary of changes, motivation and context for this PR.

There is a lot of back and forth in the build instructions in the readme for different platforms. To quickly get a set of instructions for either Windows or a Unix platform this PR arranges them into clickable sections when viewed on Github. e.g. it looks like this, where you click on the platform you want, to get the instructions just for that platform

To me this a lot cleaner, and easier for a beginner to decipher what exact instructions the user wants for their platform. To see how this looks in practice, and how it neatens everything up, see the branch of this PR https://github.com/mcbarton/CppInterOp/tree/Neaten-readme-build-instrucgtions

Fixes # (issue)

Type of change

Please tick all options which are relevant.

• Bug fix
• New feature
• Requires documentation updates

Testing

Please describe the test(s) that you added and ran to verify your changes.

Checklist

• I have read the contribution guide recently

[mcbarton]

Will work out how best to fix the linter issues next week (almost all about now having duplicate headers). Feel free to provide feedback on the idea of the PR in the meantime though. I will stop the workflows for now, and they can run when I fix the linter issues.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.52%. Comparing base (82f08c6) to head (c4b4da9).
⚠️ Report is 45 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #664   +/-   ##
=======================================
  Coverage   79.52%   79.52%           
=======================================
  Files           9        9           
  Lines        3917     3917           
=======================================
  Hits         3115     3115           
  Misses        802      802           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mcbarton]

Now that the markdown linter is passing for this PR it is ready for review.

[Vipul-Cariappa]

This looks good, will help beginners.
I was thinking; should we have nested expandable sections, for cling & clang-repl?

[mcbarton]

This looks good, will help beginners. I was thinking; should we have nested expandable sections, for cling & clang-repl?

Thanks for the feedback. I was thinking about this idea already, and will implement it sometime this week.

[mcbarton]

@Vipul-Cariappa I have applied your suggestion if you want to take another look.

@vgvassilev pinging for a review. This PR changes how the build instructions are navigated in the readme file (by using expandable sections). Go here https://github.com/mcbarton/CppInterOp/tree/Neaten-readme-build-instrucgtions to see what it would look like.

[Vipul-Cariappa]

This looks good to me.
I did not read the entire thing; Maybe we should specify somewhere that Clang-REPL is the preferred way to build CppInterOp, instead of Cling. @vgvassilev any thoughts?