Reorganize website docs

[mwachs5]

After realizing that the oh-so-handy Cookbook wasn't discoverable on the website, I went on a bender of finally getting rid of the "Wiki (Deprecated)" section, which turned into a bunch of docs cleanup.

This PR:

• Creates a Developers and Resources section, then moves everything out of the wiki (Deprecated) into one of the existing sections, the vast majority into the explanations category. I thought most of the content was of that sort. I did not try to split up any individual articles.
• applies mdoc checks as much as possible around all the code snippets and corrected a few things found in this way
• moved all the .md "landing" pages for each section from the website repo directly to here for a more consistent editing experience, and put links on each of them to the content
• Broke up the "Introduction" section into "Introduction" and "Motivation".
• Added the information about loading memories into the Experimental Features section
• I somewhat cleaned up the FAQ section, but as it is I don't think the "how to verilog" instructions are solid enough so my website PR does not include the FAQ Cleaned up the FAQ section and added it to the Resources

Contributor Checklist

• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
• Did you delete any extraneous printlns/debugging code? -- Not yet one thing is commented out i need to debug.
• Did you specify the type of improvement?
• Did you add appropriate documentation in docs/src?
• Did you state the API impact?
• Did you specify the code generation impact?
• Did you request a desired merge strategy?
• Did you add text to be included in the Release Notes for this change?

Type of Improvement

• documentation

API Impact

Backend Code Generation Impact

No impact on backend code

Desired Merge Strategy

• Squash: The PR will be squashed and merged (choose this if you have no preference.

Release Notes

Documentation reorganized, wiki content redistributed.

Reviewer Checklist (only modified by reviewer)

• Did you add the appropriate labels?
• Did you mark the proper milestone (3.2.x, 3.3.x, 3.4.0, 3.5.0) ?
• Did you review?
• Did you check whether all relevant Contributor checkboxes have been checked?
• Did you mark as Please Merge?

[jackkoenig]

Overall this looks good, I do have a couple of questions / comments

[jackkoenig]

I'd also like to note my comment here: #1805 (comment) There's at least 1 page still existing on the Wiki that doesn't exist on the website.

[mwachs5]

"I'd also like to note my comment here: #1805 (comment) There's at least 1 page still existing on the Wiki that doesn't exist on the website." -- added this content under the experimental features section

[mwachs5]

@jackkoenig , @seldridge I think I am ready for a review on this. There is one unresolved change moving from chisel3.Driver to ChiselStage. This is also seemingly failing CI due to inability to grab dependencies.

[mwachs5]

Found the remaining question I had about getting the annotations example to work (@azidar , @jackkoenig ?)

[jackkoenig]

This is fantastic, thank you so much @mwachs5! I have a few suggestions but this is a huge improvement!

[seldridge]

Amazing.

Thanks for tackling this @mwachs5!

[jackkoenig]

I've realized why the links don't work if we put .md at the end of them but they did once before. Previously, all of this mdoc was in the website repo and sbt-microsites specifically supports pointing to your mdoc. I'm assuming they do the whole "link to md converted to link to html" conversion for you. Not yet sure how to solve, but I think that's the cause.