Copy metadata to cache instead of moving it

[jonesbusy]

• Copy metadata to cache instead of moving it
• Add attribute on recipe to force the rebuild
• Store the metadata on the pom.xml so it can be consumed

Idea is to not "manually" perform metadata collection before a recipes but add is as a first recipe.

So that later recipes applied on the trees can lookup for the marker instead of relying of ready manually the data from any storage

The build-metadata` will remains to force the rebuild on populate the local storage

Testing done

Automated tests

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[jonesbusy]

Still evaluating if the search flag is relevant to print the search result back to code.

I will most likely keep the Marker implementation for the plugin metadata and remove the search result.

This is because scanning recipes cannot be used as preconditions. So it means we will need to add the recipe as a first recipe of each declarative recipes.

The IsUsingBom condition has been adapted to use this approach