This has bit me more than once. It's best just to make Mirage consistent
with the API even if it currently means indeterminate job ids

By default, blocks have a margin of 1.5em to create a consistent
vertical rhythm. However, sometimes elements need to be associated with
the element above them. In this cases, the gap between elements needs to
be tighter. There are many ways to do this, but this approach asks the
latter content to be marked as associative. The implication is that the
association is with the previous block.

UI: New JSON viewer

Borrowed heavily from Vault

UI: Region Switcher

This is a more idiomatic way to handle the QP resetting in the
application controller.

vendor: fix blake2b on non-amd64 archs

Skip update checking if DisableUpdateCheck is set to true

Base go-plugin client/server

Convert HCL Interface values to Cty Values