Resolves #855: Set should evaluate expressions

[andrzejj0]

Fixing a regression after #799

The premise of that PR was that the mojo was updating every file if it did not find any match anywhere. This made the mojo update files where e.g. the version was specified as a parameter.

The fix does it differently -- by resolving parameters and checking if they match the artifact coordinates.

[andrzejj0]

@slawekjaranowski please review

[andrzejj0]

@pzygielo @slachiewicz @slawekjaranowski do you think there might be other corner cases to check here?

[pzygielo]

@ajarmoniuk thanks for asking, but I'm not advanced user of versions-m-p nor I know the codebase well.
It looks that feedback from community is pretty fast though 😄

[andrzejj0]

Sławek's question is valid though -- perhaps this PR is not needed after all.
On the other hand, it does fix the issue :)

[slawekjaranowski]

a Corner cases from https://maven.apache.org/maven-ci-friendly.html

Property as:

 <properties>
    <revision>1.0.0-${buildNumber}-SNAPSHOT</revision>
  </properties>

version with multiple properties:

<version>${revision}${sha1}${changelist}</version>

Multi Module example

[andrzejj0]

@slawekjaranowski added these corner cases

[slawekjaranowski]

On more test will be appreciable:

Parent with property:

 <parent>
    <groupId>org.apache.maven.ci</groupId>
    <artifactId>ci-parent</artifactId>
    <version>${revision}</version>
  </parent>

[andrzejj0]

Assuming you meant a parent with a property with a child module -- added.