[runtime] Support for storageSize, storageType, zone, and subZone

[ssmirr]

Allows for leveraging the lower-level features of the platform to customize the scheduling and storage of runtimes, such as Besu and IPFS.

[ssmirr]

Noticed the CI build is failing, but unlikely to be related to this specific PR as there seems to be a few other failures before this build.

Current findings are:

• that the expected API calls made by the provider are different depending on the version of terraform CLI installed
• the build is passing for locally (macOS) with terraform v1.8.5 however same terraform version is currently failing in this PR because expected and actual API calls are different
• I'm able to reproduce the failure locally by running tests in act's Docker containers (simply running $ act in this repo) so one possibility might be a difference in Linux vs. macOS releases of terraform (?)

I will keep looking and update here if I find something more interesting by tonight

[onelapahead]

#79 helped rule out what was going on with the tests - it was broken due to the missing terraform CLI install in the workflow.

But the resource / tests had a few bugs in the optional vs computed logic for the storage related fields which are optional for the user, and are only relevant for certain runtime types.

I updated the test to manage a runtime with a specified zone, storage type, and storage size for now. Additional tests for non-storage runtimes and zone defaulting would be helpful in the future.

[onelapahead]

Our API should always returns this, so if its false we still want it in serialized JSON responses. Otherwise it was being omitted and the unit tests were broken.