Parent container with child application

### Current Behavior

Working for a large company, I'm part of a team of 70 developers working on 1 large application divided into sub-applications. We use DependencyTrack to analyse vulnerabilities in our applications and track the number of vulnerabilities from release to release.
However, I'm currently having problems using DependencyTrack to work effectively.
As you can see on the attached screen, I use DependencyTrack to analyse ALL my projects. Each of our projects has a "release" version and a "development" version.

The problem I'm having is the hierarchical organisation of DependencyTrack. It is impossible to create "applications" that are children of a parent "container".

In my screen, you can see that I have to use an alias on each child container to avoid having a creation ban because the name is already taken. So I end up with a very complex and, above all, long hierarchy.


### Proposed Behavior

The expected behaviour would be as follows:
- When creating the "project", don't just check that the name exists to refuse creation, but join this check with the parents.
For example, it would be possible to do the following:
Project 1 -> Development -> 1.1
Project 2 -> Development -> 1.1

- Do not use any classifier for a parent

### Checklist

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this enhancement was already requested