Implement script versioning

[KSemenenko]

Summary

Implement script versioning to reference past drafts or revert changes. Consider replacing generic tags with the script's current version count.

Source

• Category: Script Editing
• Feedback video: https://youtu.be/IeUoMyx7dKE?t=26m51s

Acceptance criteria

• Users can see script version history or version count for draft changes.
• Users can reference or restore past drafts without leaving the browser-first local workflow.
• Generic version tags are replaced or supplemented by meaningful version count/status where applicable.
• Add or update browser/UI test coverage for the relevant user flow.
• Solution tests pass before the issue is marked ready for user verification.

[KSemenenko]

Ready for user verification on local main at cef8cf9.

Verified implementation:

• browser-local script revision history is available from the editor tools/sidebar panel;
• the panel shows autosave state plus a meaningful local history count;
• users can restore earlier local revisions without leaving the browser-first workflow.

Relevant coverage includes EditorLocalRevisionStoreTests, EditorLocalHistoryInteractionTests, and EditorLocalHistoryFlowTests.

Validation run:

• dotnet test @./tests/dotnet-test-progress.rsp --solution ./PrompterOne.slnx: passed, 1191/1191
• dotnet publish ./src/PrompterOne.Web/PrompterOne.Web.csproj -c Release -o ./.artifacts/prompterone-publish -p:PrompterOneBuildNumber=0: passed

Release-version comment still pending after the release that ships this.

[byskyphy]

Implemented but I'd rather see a diff view thatn open previous or click to restore : these aren't as useful when tracking changes of the script you wrote.

this is not a priority for now.