`quick-comment-edit` - Issue with list item description fails on re-edit button press (10003)

repro for https://github.com/refined-github/refined-github/issues/10003

Description

[!NOTE]
For simplicity, : is used as separator in below description, but other character(s) combinations could be used.

Allow : as a prefix/namespace separator to allow categorization, such as measurement:distance, measurement:area, etc., which offers an abstract grouping of processes, with low impact on the actual API endpoints definition.

This nomenclature has been proposed in the past (see process endpoints under section https://docs.ogc.org/per/20-016.html#terradue-dapa).

The : should be handled properly to distinguish it from its similar use for {processID}:{version} referencing.

Furthermore, the : prefix should not be limited to one item, but should allow any amount of namespace definitions, such as dev:testbed:measurement:area.

Considerations

• A :: may be considered to avoid possible clashes with {processID}:{version} or other remote/provider process IDs that could already employ : (itself using namespaces or URN as process IDs).
• The specific pattern of ^(.*):(?P<MAJOR>[0-9]+)\.(?P<MINOR>[0-9]+)\.(?P<PATCH>[0-9]+)$ might be enough to distiguish :-namespaced from :-revisioned uses of the same separator.
• The selected separtor should not introduce ambiguities/breaking behaviour with existing databases that store
  "identifier": "{processID}:{version}" of older revisions for direct access.

References

• Details for {processID}:{version}: https://pavics-weaver.readthedocs.io/en/latest/processes.html#modify-an-existing-process-update-replace-undeploy (documentatation to be updated accordingly)

No repository files or tests are named. Start with the referenced process-endpoint documentation and the existing handling of {processID}:{version}; clarify the namespace and separator rules, compatibility with stored identifiers, and the acceptance cases before implementation.