Filter projects/environments from EclipseLauncherProvider

[d-gs]

Feature request

Expected Behavior - What were you expecting to happen?

Some projects/environments might not require an eclipse configuration (e.g., if a thirdparty plug-in or eventually a core one provides a different way to open the workspace, or a workspace is not required).

Current Behavior - What happens?

If Eclipse plug-in is provided, all environments/projects provide the launcher(s) even if they are not relevant nor configured.

Possible Solution

1. Filter for projects/environements IDs provided on the eclipse config
2. Rely on the oomph setup files (project catalog) and if not present does not show the Eclipse launcher

Context

Configuration for extension plug-in