update: change CSV alm-examples

[VanillaSpoon]

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
During release, the community-operators-prod sync is failing with:

[static-tests : run-suite]     {
[static-tests : run-suite]       "type": "error",
[static-tests : run-suite]       "message": "CSV contains an invalid value for metadata.annotations.alm-examples",
[static-tests : run-suite]       "check": "check_required_fields"
[static-tests : run-suite]     },

this is due to the following check:

        ("metadata.annotations.alm-examples", re.compile(r".{30,}", re.DOTALL), True),

A resolution is to add an alm-examples for the AppWrapper CRD

New Submissions

• Are you familiar with our contribution guidelines?
• Are you familiar with our operator pipeline?
• Have you tested your Operator with all Custom Resource Definitions packaging?
• Have you tested your Operator in all supported installation modes?
• Have you considered whether you want to use semantic versioning order?
• Is your submission signed?
• Is operator icon set?

Your submission should not

• Add more than one operator bundle per PR
• Modify any operator
• Rename an operator
• Modify any files outside the above mentioned folders
• Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

1. Description of the managed Application and where to find more information
2. Features and capabilities of your Operator and how to use it
3. Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

• Human readable name and 1-liner description about your Operator
• Valid category name¹
• One of the pre-defined capability levels²
• Links to the maintainer, source code and documentation
• Example templates for all Custom Resource Definitions intended to be used
• A quadratic logo

Remember that you can preview your CSV here.

--

¹ If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need

² For more information see here