Issue 666: Add UcoType and Technique

[ajnelson-nist]

This Pull Request resolves all backwards-compatible requirements of Issue #666 .

Coordination

• Pull Request is against correct branch
• Pull Request is in, or reverted to, Draft status before Solutions Approval vote has passed
• Documentation confirmed to render metaclass
• CI passes in UCO feature branch against develop
• CI passes in UCO current unstable branch (fdc106b)
• CI passes in CASE current unstable branch tracking UCO's unstable as submodule (36886a9)
• Impact on SHACL validation reviewed for CASE-Corpora
• Impact on SHACL validation remediated for CASE-Corpora (N/A)
• Impact on SHACL validation reviewed for CASE-Examples
• Impact on SHACL validation remediated for CASE-Examples (N/A)
• Impact on SHACL validation reviewed for casework.github.io
• Impact on SHACL validation remediated for casework.github.io (N/A)
• Milestone linked
• Solutions Approval vote logged on corresponding Issue (once logged, can be taken out of Draft PR status)

[ajnelson-nist]

In the last call, we'd left a note-to-selves to confirm the documentation would render this implementation.

I can confirm the documentation renders as at least I expected. Unfortunately, I can't think of a clean way to "Preview" the documentation aside from suggesting any interested reviewers pull down local HTML pages themselves. The generated documentation, with static HTML, is in this branch, and pages can be opened from local disk without executing anything. E.g.:

• documentation/class-ex1technique.html - see the metaclass ex1:Technique, which specializes uco-action:Technique.
• documentation/class-ex1technique-t0001.html - see an instance of Technique.

This engine does not appear to support any particular emphasis that the class "T0001" is an instance of a different class hierarchy. The Turtle snippets excerpted from the ontology at the bottom of class pages do include the instance-of-something-custom designation (ex1:Technique-T0001 a ex1:Technique, owl:Class ; ...), but nothing else really visualizes a bridge from class to metaclass. This is not intended as a criticism - it just doesn't seem to have been a feature on the engine's radar.

[ajnelson-nist]

This PR is ready for review and merge. Please, to the requested reviewers:

• Please do not merge before CI passes on commit 871bb29.
• As requested, "SOP" and "procedure" have been removed from the new tests, but to avoid confusion I just put "Technique" back in under the second example-organization's namespace, avoiding synonyms. If it's too confusing because of term overuse, please do suggest another synonym.
• If CI has passed and the other review has Approved, the second reviewer should feel free to merge when they approve.