[IDEA] Update aem-api dependency to use latest available version

*This is more of an idea discussion thread, that could be turned into an enhancement if it makes sense.*

It might be nice to provide a way in the maven archetype to:

+ Build using the latest `aem-api` dependency, using an open-ended version range like `[2020,)`

The logic being, Cloud Manager builds the project using the `aem-api` dependency version specified in the project, but this version does not (and in fact, rarely) matches the version of AEM being deployed to - especially on auto-updating AEM envs.

Pinning a version (as we do today) could be useful for those that want to deploy to a fixed Sandbox or non-production env (that they let sit on an old version, which again, is not ideal).

Understandably, there may be some trepidation about constantly and unknowingly changing the dependency version you're building/testing against, but Adobe promises the `aem-api` is backward compatibility, so IIUC this is should never be problematic (and break a build/behavior).

Start by examining the Maven archetype's dependency configuration and how the current aem-api version is pinned. Determine whether an optional open-ended version range can be offered while retaining a fixed-version path, then verify the generated project builds correctly for both choices.

Written by the indexing model from the issue text.