Update devfiles processes after alizer migration

[thepetk]

Which area/kind this issue is related to?

/area alizer

Issue Description

• Create label for alizer -> area/alizer
• Create the initial alizer release for the new repo (v1.0.0) after the new project's structure.
• Update all issue templates inside devfile API in order to include this new label.
• Copy all issues from alizer to the devfile/api repo. Include a link to the old issue. Finally, add them to the devfiles project
• Close all open issues inside alizer and link them with the devfile ones.
• Update the documentation of sprint boss and the daily agenda.

Target date: 30 June 2023

[thepetk]

The new label area/alizer is already created along with the initial release of the new alizer repo (v1.0.0).

The PR for updating all issue templates is #1149

[thepetk]

• The issue templates have been updated
• All issues have been copied to devfile/api and they were added to devfile project
• All issues were closed on the old repo

[thepetk]

All docs impacted by the migration of the repo have been updated and a deprecation warning is added to the old repo