Migrate che-operator and che-machine-exec to 'eclipse-che' organization

[flacatus]

Is your task related to a problem? Please describe.

As we speak during Eclipse Che Community call we will start to move Che related repos to new organization.

Describe the solution you'd like

In order to migrate che-operator and che-machine-exec to new organization we should consider:

• Sync all release scripts
• Install Openshift CI github application in the new organization and related webhooks
• Make sure all tests will work in the new organization

Describe alternatives you've considered

Additional context

[flacatus]

I add this consideration for now about migration to new organization. @l0rd Please feel free to change if I miss something

[sleshchenko]

cc @JPinkney
since WTO should be adapted to these changes as well.

[sleshchenko]

I assume it's cheap if in the scope of this issue to migrate to main default branch (instead of master)

[l0rd]

Can we avoid moving chectl? I am afraid that porting it to an eclipse foundation repo would require a review of the telemetry data we are collecting as well.

[flacatus]

@tolusha @l0rd @sleshchenko Bugzilla opened: https://bugs.eclipse.org/bugs/show_bug.cgi?id=571912

[nickboldt]

Downstream issue for how this impacts CRW and how to adapt to the change: https://issues.redhat.com/browse/CRW-1661

[nickboldt]

Can we avoid moving chectl?

Wouldn't that also require an incubation exit review, with all the attendant Eclipse Foundation paperwork and process?

[nickboldt]

Adding blocker label since as we start this change, we block Che and CRW releases, which means implementing solution to the change will be high-priority work (too bad we still don't have priority labels, eh @l0rd ? :D )

[benoitf]

hello, please ensure https://github.com/eclipse/che/blob/master/.repositories.yaml is up-to-date as well

[tolusha]

thank you.
#19353