Add a dynamic_reference seedtype

[jkomoros]

This would allow calculating the ID to include

Type: dynamic.

A reference property that expects an object, and will interpret it like a SeedReference. (Wait, won't the engine interpret a reference as a reference to execute?). Maybe reference should be a packedSeedReference. (That has the benefit that it's not interpeted by the rest of the machinery as a reference)

Make sure the use case of "pass in a seed graph root to execute" works.

Update documentation for things like seed.references() to make it clear that it does not include dynamic seed references.

dynamic should have a allow_remote property. Unless it's set to true, then a reference that goes to a remote packet won't load.

• Add reference, which takes seed_id and packet, and auto-merges the current location of the seed and returns a packedReference.
• Add dynamic, which takes a reference (test to make sure it rejects remote calls
• Mermaid diagram should render dynamic in green
• Add an allow_remote optional boolean to dynamic.
• Don't fail remote access if the remote packet is already loaded.
• A way to set a secret key of disallow_remote that seeds can't read back, but sub-seeds below that point in environment will throw if a remote is tried to access even if allow_remote. And that's true for seed references that are direct
  • It's not so much secret as much as a key that can never be set to false. It starts as false but then can only be set high.
  • (Same thing for Add a fetch seed_type #45, just with disallow_fetch )
• Add an example ot example-complex.json