BUG: Build action message keys aren't conducive to suppressing them

[ekoniec1]

Description

When tailoring a project to exclude aiSSEMBLE-generated components that aren't needed for that project, unnecessary build notifications cannot be easily suppressed. For example, consider a project that doesn't need a PDP - adding *-policy-decision-point-docker to .gitignore and omitting PDP Helm chart generation Fermenter goals in -deploy/pom.xml is a reasonable first approach instead of creating a new set of Fermenter generation targets/profiles that exclude PDP artifacts. Following the guidance emitted guidance on message suppression:

[WARNING] To disable specific messages, please add their message keys to the suppressedMessages list. See the Fermenter docs for more info: https://github.com/TechnologyBrewery/fermenter

Executing the build with the -Dfermenter.display.message.keys=true flag yields message keys that aren't portable and contain absolute file path references:

[WARNING] ------------------------------------------------------------------------
[WARNING] Manual Action ##
[WARNING] ------------------------------------------------------------------------
[WARNING] Message Key: /Users/my-user-name/path/to/project/baz/baz-deploy/pom.xml_execution_policy-decision-point
                    <execution>
                        <id>policy-decision-point</id>
                        <phase>generate-sources</phase>
                        <goals>
                            <goal>generate-sources</goal>
                        </goals>
...
[WARNING] ------------------------------------------------------------------------
[WARNING] Manual Action ##
[WARNING] ------------------------------------------------------------------------
[WARNING] Message Key: /Users/my-user-name/path/to/project/baz/baz-docker/pom.xml_module

You must add the docker modules to baz/baz-docker/pom.xml to activate them in your build!
Example:
    <modules>
        <module>baz-policy-decision-point-docker</module>
....

As a result, most extraneous messages can't be suppressed in a consistent manner across developer workstations.

Steps to Reproduce

1. Instantiate a new aiSSEMBLE project with pipeline(s)
2. Execute mvn clean install -Dfermenter.display.message.keys=true before following instructions in build notifications
3. Note how the emitted build notification message keys contain absolute paths

Expected Behavior

Build notification message keys to be emitted in a way that allows them to be portably suppressed.

Actual Behavior

Most (but not all) build notification message keys contain absolute file path references which prevents them from being ignored using Fermenter's message suppression feature

Additional Context

• aiSSEMBLE version: 1.7.0
• Relevant Fermenter issue that implemented configurable message suppression