actions-lock.json - consider renaming

[dsyme]

per discussion on slack

[pelikhan]

the actions-lock.yml file is a cache of resolved action -> version -> sha . It servers as a way to stabilize the compilation process regarless of the "ability" of the github token used to compile. Resolving sha requires scanning releases and this will fail commonly in CCA, but will work fine with the user PAT or the github actions PAT. Not storing this cache of sha, creates an unstable compilation which breaks the CCA-based editing.

[dsyme]

Copilot please add this info to FAQ and Compilation docs

[pelikhan]

@dsyme how about moving/rename to .github/workflows.

It is really a "resolved-actions-pins.json" file more than a lock.

[dsyme]

It's a strange file. It's purpose is like "If you compile again with exactly the same compiler version you will get the same resolution without needing to do a version --> SHA resolution for something you may no longer be able to access, e.g. CCA. But if you use a new compiler version you'll need to re-resolve."

My feeling is the information can just go in generated workflow. We already scrape the stop time from generated workflow to keep compilation stable. This feels similar.

[dsyme]

reopening to discuss further