fix: invalid warnings when running the Dekorate session

[Sgitario]

There are some system properties that are not directly mapped using generators like dekorate.build or dekorate.push. These properties will either enable some special handling, functionality and/or include some other properties.

The problem is that at the moment, the session is checking whether these properties are properly mapped and if not, it will trace a warning.

Therefore, as these properties are programmatically used and there are many more like dekorate.input.dir, dekorate.output.dir, dekorate.image-pull-secrets, dekorate.properties.profile, dekorate.verbose, dekorate.test.xxx, ... and maybe more coming in the future, I think the best way is to not trace this warning ever.

The alternative is to maintain a list with all the above values, however I don't really like this approach as this list will be likely became out-date when adding a new unmapped property.

Fix #995

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[iocanel]

Not providing feedback to the user because it's not convinient does not seem right.

As described in #995: I would either handle those cases or even ensure that the properties are properlly backed by configuration objects.

BTW, why didn't we have this issue before: 62aab5b

[Sgitario]

Not providing feedback to the user because it's not convinient does not seem right.

As described in #995: I would either handle those cases or even ensure that the properties are properlly backed by configuration objects.

BTW, why didn't we have this issue before: 62aab5b

Before, it was raising exceptions when a configuration was not using a generator, not by a warning trace.

I don't totally agree with you about this is something we should tell users.
As you said maybe the best way to handle these unmapped properties is to actually map them using configuration objects, however as there are many unmapped properties, this is going to become a huge task. So, I will close this pull request and unassign the issue as I don't have this time right now.

[iocanel]

Before, it was raising exceptions when a configuration was not using a generator, not by a warning trace.

Indeed, still no error was thrown when -Ddekorate.build=true or -Dekorate.push=true was passed.
Anyway, I prefer getting this right even if it is a huge task.