feat(desktop-modeler): create template versioning section

[nikku]

Description

This PR ensures improves the existing template definition documentation:

• Provides linking of template parts (engine and version)
• Introduces a template version documentation
• Link to upstream documentation where it provides value

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• This is already available but undocumented and should be released within a week. (add available & undocumented label)
• This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
• This is part of a scheduled alpha or minor. (add alpha or minor label)
• There is no urgency with this change (add low prio label)

PR Checklist

• My changes are for an upcoming minor release and are in the /docs directory (version 8.8).
• My changes are for an already released minor and are in a /versioned_docs directory.

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[github-actions]

👋 🤖 🤔 Hello, @nikku! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.7/.

• docs/components/modeler/desktop-modeler/element-templates/defining-templates.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[philippfromme]

I like the general direction but following the link and seeing the graphics at https://github.com/bpmn-io/element-templates/blob/main/docs/LIFE_CYCLE.md#overview I think we could improve that (I find it hard to comprehend without screenshots) or just link to the existing documentation that covers the entire lifecycle (though engine compatibility is currently missing). I think we need to cover 5 different states: https://miro.com/app/board/uXjVI1a7lHU=/

[nikku]

I think we could improve that (I find it hard to comprehend without screenshots)

@philippfromme What is hard to comprehend about the graphics? Keep in mind this is developer, not user documentation.

[philippfromme]

I guess it's just me. 😅

[christinaausley]

@philippfromme I will keep an eye on this page with PushFeedback (which tracks incoming feedback from users on each page) to see if we get any additional thoughts on this. For example:

On the backend I can see if anyone leaves comments with their thumbs up/down as well.

@nikku Is this still a WIP or ready to be moved out of draft and merged?