…Server`

…8c91ecdedc494b3fc0c0eaf3

… hooks.

Add builder API to customize a `JiraNodeFlow` rather than replacing it.
The alternative is to only keep the replacement API, but we need a compact way to get the default as a caller.

They can hook per instance rather than per node.
There are two timings now: "pre-provision" and "instance URI available".
They also have access to node hooks.

…8659c0

Bump infra to 99198b597776318aadc02b19b3123d8b03415dee

Bump infra to be7978ed60b8bf903483d33e82562a3444e08ff8

Start working on `Infrastructure` based on `Future<ProvisionedStack>`.
It should be able to split into dedicated sub-infras for DC nodes,
mysql, LB.
Use `NfsSharedHome` from infra.

Open question: who should decide which ports should be open:
* `Infrastructure` impl because the network setup already exists for BTF or
shared CloudFormation stack?
* consumers of `Infrastructure`, because MySQL knows it works on 3306
and Samba knows it works on TCP 139, 445 and UDP 137, 138
* both, where consumers give hints, but infra has the last word?

infrastructure snapshot from 290dd1bfea2291cbf05e88f47610c15ba4528c72

Bump infra to 79b89cfb841dec34ce66e31b03ba6dbd477d2084

Open problems:
* plans shouldn't use resources, but some sub-plans require resources,
    * e.g. `Ec2ServerRoom` (and others) require `SshKey` and `Vpc`
    * make a "common resources" container and pass it via methods?
    * OR figure out resource passing via constructors (like `Future<SshKey>`?)
* HTTP -> TCP -> SSH dependency chain doesn't match the real layers
    * in reality SSH depends on TCP 22, not the other way around
    * the problem is seen between `Ec2ServerRoom` and `AwaitingEc2`
    * maybe we need to model multi-ports in TCP? but how to distinguish
      HTTP 80 port from SSH 22 port or 3306 MySQL port? Samba needs many
* `AutoCloseable` vs `Resource` for deprovisioning

make it work, then refactor
* maybe extract SSH/nonce/workspace/investment/network
  as a common resource and reuse across *separate* Jira/LB/VU

Build a bridge between LB formula (AWS) and LB plan (SSH).
Copy `TokenScrollingEc2` from `aws-resources`.
Bump infra to b6a4576d5059c323ad71ba55f9cb5a6151e097e3 to call
preinstance hooks in parallel.
Reuse `StackJiraNodes` instance, because it's stateful right now.
Make `LegacyAwsInfrastructure` cheap to construct by deferring
networking.

Consume infra ce8c26cd471ffe981bfb791be7fc218acf948e51

Next steps:
* pristine Jira DC Plan unencumbered by `LegacyAwsInfrastructure` or CFN
* bridge from `JiraInstancePlan` to `JiraFormula` if possible
* bridge the other way around if possible
* can `SambaSharedHome` really work with just `TcpNode`?
* do we actually need `Reports` transport via S3?
* do we need bulk/directory transport for `Reports`?
* add jpt-workspace as CI artifact
* make hook collections append-only (`PreInstanceHooks` already are)