Alizer enricher support for devfile port detection and default framework ports

[thepetk]

/kind user-story
/kind epic

Which area this user story is related to?

/area alizer
/area documentation
/area test-automation

Which functionality do you think we should add?

This EPIC is the second part for the implementation of the devfile port detection functionality (full description here). In this part we focus only to the enhancements required on the enrichers and the detectors of alizer. As a result, in order to proceed with this EPIC we first need to complete #1154 because we will need first to have support for the devfile library.

Describe the solution you'd like

Having in mind that alizer will be using (or already uses) the devfile library to detect ports from devfiles, we will now need to update the enrichers & detectors side in order to use this feature when someone runs the component command. Therefore, the required steps to complete this epic are:

• Add new strategy inside the component command in order to include the devfile as PortDetectionAlgorithm.
• Update all enrichers to use an extra case for the devfile strategy. In order to ensure backwards compatibility we will not add this strategy by default.
• Last part of this epic is to add support for the default ports. So on every detector we will need to have a specific function that will return the default ports, while updating the DoPortsDetection function.

Acceptance Criteria

• Implement alizer support for devfile port detection #1331
• Add strategy for devfile port detection to alizer enrichers #1156
• Support alizer default ports per framework #1157

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

[thepetk]

Still a requirement :)