Simplify adding *-image profile configuration

Given that the profile declarations are in the helidon-se or helidon-mp parent poms, adding configuration in the application pom is either verbose or somewhat ugly.

The ugly solution is to use global properties with fully qualified names, e.g.

<native.image.buildShared>false<\native.image.buildShared>

The more natural solution is to use a configuration element:

<configuration>
    <buildShared>false<\buildShared>
<\configuration>

The only way I know to add that configuration and retain the profile behavior is by duplicating the parent <profile> declaration. Hopefully there is a less verbose way to do this.

[batsatt]

We won’t get completions, but you can already just set properties in the pom; this is certainly the easiest thing to document.

[batsatt]

Yes, we could do that as well, although you obviously have to navigate to the parent to see them.

We still need our docs to point at something that describes each property, though; Joe’s new docs point at the plugin docs for this.