Update nodejs-nextjs stack

[RomanNikitenko]

What does this PR do?:

Updates nodejs-nextjs stack:

• Add new version: 1.2.1
• Set schemaVersion: 2.2.2
• Set https protocol for the endpoint
• Set 1.2.1 version as a default one

Which issue(s) this PR fixes:

eclipse-che/che#22869

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:

You can use the following link to start a workspace for testing:
https://workspaces.openshift.com/#https://raw.githubusercontent.com/RomanNikitenko/registry/update-nextjs/stacks/nodejs-nextjs/1.2.1/devfile.yaml

Signed-off-by: Roman Nikitenko rnikiten@redhat.com

rh-pre-commit.version: 2.2.0
rh-pre-commit.check-secrets: ENABLED

[openshift-ci]

Hi @RomanNikitenko. 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]

/retest

[michael-valdron]

@Jdubrick we'll need to rebase to your changes

FYI @RomanNikitenko

[thepetk]

Looks good to me, the reason of the PR checks are failing is devfile/api#1494

Not sure if we would like to remove completely version 1.2.0 (remove the dir and its record in the stack.yaml) like we did in #342

cc @michael-valdron @Jdubrick

[thepetk]

@RomanNikitenko could you try to rebase with the latest main. That should fix the ci failure for odo3 check

[michael-valdron]

Not sure if we would like to remove completely version 1.2.0 (remove the dir and its record in the stack.yaml) like we did in #342

@thepetk Prefer we don't completely remove stack versions but rather deprecate them.

[thepetk]

/lgtm @michael-valdron sgtm to keep the 1.2.0 as is and deprecate it soon. Tested locally and is ok.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RomanNikitenko, thepetk

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 [thepetk]

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

[RomanNikitenko]

could someone merge
I don't have merge permissions...

thanks in advance!