Support versioning of Meshery designs

[Yashsharma1911]

Current Behavior

Meshery designs are not automatically versioned by Meshery Server.

Desired Behavior

General Description

• Update Meshery server and pattern engine to support Meshery design versioning.
• Update UI to allow users to perform actions related to design versioning.
• Document changes made in pattern engine and server.

Specific Requirements

1. The minimum viable feature here is simply a semver-compliant version number.
2. The version number should be auto-incremented each time the design is saved (updated).
3. The version number should not be incremented upon import, but a version, e.g. v0.0.1, assigned if none is present.
4. The version number should not be incremented upon export.
5. The version number should be displayed, but not editable (should be read-only).

Implementation

1. [Server] ....
2. [UI] ...

Recommended Skills:

Golang, Kubernetes, Meshery, Familiarity with Helm charts and Artifact Hub, familiarity with React, Nextjs would be helpful

Future enhancement:

1. The version number may not be edited, in Meshery UI so long as the number supplied is validated semver-compliant and does not regress in numbering.

Acceptance Tests

1. Upon export with existing version...
2. Upon export with no existing version...
3. Upon import with existing version...
4. Upon import with no existing version...
5. ....

Mockups

---

Contributor Guides and Handbook

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[github-actions]

This issue has been labeled with 'component/ui'. 🧰 Here are docs on Contributing to Meshery UI. 🎨 Here is the Meshery UI Figma File File. Lastly, here are docs on Contributing to Meshery's End-to-End Tests Using Cypress.

---

        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄

[leecalcote]

I marked this as an epic. Depending upon who works on this, it'll need child issues created. It'll also need a design spec to include the following along with other considerations:

1. The minimum viable feature here is simply a semver-compliant version number.
2. The version number should be auto-incremented each time the design is saved (updated).
3. The version number should not be incremented upon import, but a version, e.g. v0.0.1, assigned if none is present.
4. The version number should not be incremented upon export.
5. The version number should be displayed, but not editable (should be read-only).

Future enhancement:

1. The version number may not be edited, in Meshery UI so long as the number supplied is validated semver-compliant and does not regress in numbering.

Edit: I updated the description to include this information.

[github-actions]

This issue has been labeled with 'design-required'. Note that prior to commencing on implementation, a design specification needs to be created and reviewed for approval. See Creating a Functional Specification to create a design spec.

---

        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄