Isolate sudo usage

[abejgonzalez]

Eventually, we want to make FireSim not depend on sudo, and if it does, then it should only do sudo operations during system setup (i.e. when installing FPGAs). This will isolate the spread of sudo throughout the codebase and instead focus it on a few functions. This will allow local setups to not depend on passwordless sudo (which generally isn't a good practice).

For non-AWS setups, there is now a "sysadmin" step where you install FireSim scripts to /usr/local/bin that are used by the manager. This PR does the following:

• Fixes the CI so that we can run U250 CI simulations. Now checks single-core Rocket/BOOM and multi-core Rocket Linux boots.
• Updates the CI to build more images and use new machines.
• sudo is removed in as many places as possible (really only needed during AWS now)

Misc. TODO:

• Should work for U250 setups (single node)
• Should work for U250 setups (switch-based simulations)
• Should verify that AWS simulations work (single node)
• Should verify that AWS simulations work (switch-based simulations)
• Need to update the docs. (See docs here: https://docs.fires.im/en/sudo-once/Getting-Started-Guides/On-Premises-FPGA-Getting-Started/Initial-Setup/Xilinx-Alveo-U250.html)
• Check things in deploy/sudo-scripts/README

Related PRs / Issues

UI / API Impact

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?

[abejgonzalez]

All simulations are now verified. On merge, I'll squash/rebase the PR.

[joonho3020]

Do you think we should we DRY out /usr/local/bin throughout the manager?
Otherwise LGTM!

[abejgonzalez]

Do you think we should we DRY out /usr/local/bin throughout the manager? Otherwise LGTM!

Sure. I was just lazy and haven't done that.

[abejgonzalez]

Ping @sagark

[abejgonzalez]

I've gotten an offline approval from @sagark on this PR. I will merge on CI passes on this.

[joonho3020]

I've gotten an offline approval from @sagark on this PR. I will merge on CI passes on this.

Great stuff! Thanks for cleaning it up.