Add v80-smi static shell flashing

[amd-vserbu]

Summary

• Adds v80-smi write-static-shell so users can program the V80 static shell from packaged shell assets or an explicit PDI.
• Extends vrtd with authorized cfgmem programming, async progress reporting, and hotplug coordination for reliable flash updates.
• Packages the Vivado flashing helper and documents the new static shell programming workflow.

Usage

This PR enables:

v80-smi write-static-shell --flash --device <BDF>

or

v80-smi write-static-shell --jtag --device <BDF>
# or
v80-smi write-static-shell --jtag --no-remove-device

For jtag, the BDF is only required to remove the device from the daemon and kernel current devices list before reprogramming. For shells programmed for the first time, --no-remove-device is appropriate. If multiple devices are connected via jtag, you can/must specify a particular xsdb device_id with --xsdb-target-id.

By default, this writes the static shell from slashkit. You can specify a specific shell with --pdi.

This also allows bootstrapping without writing AVED from the Vivado GUI.

There are also no more reboots needed after writing the image.

[merkelmarrow]

This is really great, bootstrapping via JTAG has been a pain. I haven't read the code so maybe this has already been implemented, but it would be cool if this left a timestamped record of every flash's PDI hash in some persistent place automatically

[amd-vserbu]

@merkelmarrow Flash events with timestamps are written to the vrtd journal. We can add the shell hash to that log, but I'd think it's better to wait for proper shell IDs with #147

Is that appropriate or what use case do you have in mind?

[merkelmarrow]

@amd-vserbu that's perfect