Archive legacy packages and examples in new branch

[josephfusco]

As a faust.js maintainer, I want to remove any deprecated/unused areas of the codebase in order to clean up the codebase.

Acceptance Criteria

• A new branch archive-legacy exists, with legacy code for future reference
• Legacy site is no longer live, with a redirect pointing to a new page on faustjs.org, stating that the legacy markdown documentation can be viewed in the repo on the archive-legacy branch
  • New Faustjs.org /legacy route that provides info on where to find docs and the state of the legacy versions - https://faustjs.org/legacy this has been done on the new site and the current version
  • Redirect legacy.faustjs.org to new faustjs.org/legacy page.
• All legacy examples, packages, and sites, are removed from the canary branch #1988

[moonmeister]

The Archive has been created and protected. The migration guide and and legacy code removal somewhat depends on the faustjs.org site being updated to handle old requests to legacy. I'm going to add those upgrades to the new faustjs.org site work that @wpengine/developer-relations is doing. This will delay this move but our depreciation post does note that we will be "supporting" this through the end of 2024. AS the new site is suppose to be released by the EOY waiting to full depreciate the old docs seems like it can wait on that. In the mean time I'll work on updates to the repo and other things that don't depend on the new site.

[josephfusco]

Given the security issues are in the example projects, it seems we can still push the older examples into a new branch, but leaving the legacy packages in place in canary for now, updating the legacy docs to point towards the legacy branch. 🤔

[moonmeister]

@diarmuidie Do you know who/how we can get DNS changes for legacy.faustjs.org?

[josephfusco]

Note that this will resolve #1953

[josephfusco]

We will want to verify that this is completed and that #1953 is no longer in the primary branch