chore: added upper bound to parent pom range

[jarebudev]

This PR

adds upper bound version for the parent pom

• adds this new feature

Related Issues

Fixes #1417

Notes

see https://maven.apache.org/docs/3.2.2/release-notes.html

Support version ranges in parent elements ([MNG-2199](https://issues.apache.org/jira/browse/MNG-2199)) Parent elements can now use bounded ranges in the version specification. You can now consistently use ranges for all intra-project dependencies, of which parents are a special case but still considered a dependency of projects that inherit from them. The following is now permissible: <project> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.apache</groupId> <artifactId>apache</artifactId> <version>[3.0,4.0)</version> </parent> <groupId>org.apache.maven.its.mng2199</groupId> <artifactId>valid</artifactId> <version>1</version> <packaging>pom</packaging> </project> Note this requires Maven 3.2.2 so if you use this new feature it is encouraged you add a Maven Enforcer rule to your build to ensure the use of Maven 3.2.2+. 

Follow-up Tasks

How to test

[toddbaert]

cc @aepfli @chrfwow @justinabrahms

I guess this is OK, we'll just have to remember to update these if we release new parents...

We could make the upper bound exclusive of 1.0 actually, maybe that would be safer?

[chrfwow]

I agree, let's set it to exclusive 1.0