Add a 2.2.2 devfile version and set https endpoint to Python stack

[dmytro-ndp]

What does this PR do?:

Add a 2.2.2 devfile version and set https endpoint to Python stack

Which issue(s) this PR fixes:

1. outdated "schemaVersion" attribute
2. "Application not found" error when launch Python application using Dev Spaces 3.12.0 / Eclipse Che Next

PR acceptance criteria:

• Contributing guide
  Have you read the devfile registry contributing guide and followed its instructions?
• Test automation
  Does this repository's tests pass with your changes?
• Documentation
  Does any documentation need to be updated with your changes?
• Check Tools Provider
  Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

1. Open Python 2.1.0 devfile URL https://workspaces.openshift.com/#https://raw.githubusercontent.com/dmytro-ndp/registry/54b174151d16898ae07a380ef774ad46b5ad7196/stacks/python/2.1.0/devfile.yaml
2. Run terminal task devfile: pip-install-requirements after workspace has started.
3. Run terminal task devfile: run-app and open application in new tab.
4. Stop application.
5. Run terminal task devfile: debug-py and open application in new tab.

Repeat steps above with Python 3.0.0 devfile URL https://workspaces.openshift.com/#https://raw.githubusercontent.com/dmytro-ndp/registry/54b174151d16898ae07a380ef774ad46b5ad7196/stacks/python/3.0.0/devfile.yaml

[openshift-ci]

Hi @dmytro-ndp. Thanks for your PR.

I'm waiting for a devfile member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Jdubrick]

We should create a new stack for these changes as an update to the schema version is a significant update. It would be best to create 2.2.0 and 3.1.0 stacks for this. Additionally, these new stacks will have to be added to https://github.com/devfile/registry/blob/main/stacks/python/stack.yaml

cc @thepetk @michael-valdron

[dmytro-ndp]

@Jdubrick : thank you for review!

I have applied your suggestion from the comment above.

[johnmcollier]

/ok-to-test

[dmytro-ndp]

@johnmcollier : repository's tests seem to have passed.
Is there anything else I should do to get this PR merged?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dmytro-ndp, Jdubrick

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• stacks/OWNERS [Jdubrick]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Jdubrick]

/lgtm