Major re-organization to remove a ton of duplication in the U2*0 Vivado flow as well as a bunch of other QoL feature updates.

• Implementation scripts have been deduped and streamlined. Difference between 2021* and 2022/3 is that if timing is not met on the initial implementation run, then a ML-assisted implementation mode is run (same code as before). The initial implementation run shares the same code between versions.
• We now use the same strategy_{TIMING/...}.tcl scripts as aws-fpga. This build strategy flag in build recipes is now supported for all Alveo FPGAs.
• Adds support for 4 DRAM channels to the U250 flow only. In this setup, DRAM memory controllers are always synthesized resulting in 4x(~1%) ~= ~5% (est) of area lost to the controllers. Real numbers: ~8% of FPGA taken for XDMA DRAM controllers (aka all non-FireSim stuff) compared to ~5% before.
• It is now significantly easier to support more Vivado versions. U250 now supports Vivado 2023.1. Other FPGA's haven't been modified to support other versions.
• BD for U250 is now just used to generate all Vivado IP. It does not include the firesim_wrapper. Now there is a new overall top-level with the BD as a submodule with firesim_wrapper as another submodule.
• Fixes U2*0 and VCU118 XDC paths by fixing the platform config and corresponding static XDC files in the platforms areas.

This PR looks big but really isn't (a lot of files are deleted for the de-dup or moved around).

Related PRs / Issues

UI / API Impact

Same XDMA interface. Only difference is the DRAM channels.

Verilog / AGFI Compatibility

Contributor Checklist

• Is this PR's title suitable for inclusion in the changelog and have you added a changelog:<topic> label?
• Did you add Scaladoc/docstring/doxygen to every public function/method?
• Did you add at least one test demonstrating the PR?
• Did you delete any extraneous prints/debugging code?
• Did you state the UI / API impact?
• Did you specify the Verilog / AGFI compatibility impact?

• If applicable, did you regenerate and publicly share default AGFIs?

• If applicable, did you apply the ci:fpga-deploy label?

• If applicable, did you apply the Please Backport label?

Reviewer Checklist (only modified by reviewer)

Note: to run CI on PRs from forks, comment @Mergifyio copy main and manage the change from the new PR.

• Is the title suitable for inclusion in the changelog and does the PR have a changelog:<topic> label?
• Did you mark the proper release milestone?
• Did you check whether all relevant Contributor checkboxes have been checked?