Unnecessary `duplicate project name` error in 1.4.2

[rjaros]

Expected and Results

I have a project with with multiple modules and submodules and there are submodules with the same names. Nmcp 1.4.2 gives me duplicate project name error, but these modules are not published, not configured for aggregation and not even using nmcp plugin. These are just similar example applications for my library with similar submodules. I think Nmcp should skip not published modules in this check.

Related environment and versions

No response

Reproduction steps

No response

Anything else?

No response

[martinbonnin]

#239 introduces allowDuplicateProjectNames:

nmcpAggregation {
  // Disable the check for duplicate project names
  allowDuplicateProjectNames.set(true)
}

Note that I'm not sure how to check whether the modules are published or not without configuring all of them which doesn't sound great.