Clear relationship between ephemeral and persistent lifecycle IDs

[sourishkrout]

When we first introduced lifecycle identity, it was designed to turn persistence on or off at build time. The following changes will ideally allow clients to toggle persistence dynamically.

1. Always use ephemeral IDs if there are no persistent IDs in the document/node models.
2. Decide persistence exclusively at deserialization time in the Parser.

I have cleaned up runme fmt as part of these changes, changed to run code-server in docker-only (avoid rate limiting locally), and made runme terminal stop flaking when run inside of Docker.

[sourishkrout]

The next thing to figure out is if it makes sense to harvest some of #558 into this PR.

[sourishkrout]

The next thing to figure out is if it makes sense to harvest some of #558 into this PR.

Based on my findings, I think we should forgo #558 because it does not solve the problem on the extension side.

[sonarcloud]

Quality Gate passed

Issues
6 New issues
0 Accepted issues

Measures
0 Security Hotspots
85.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud