poly info command does not list components under lower level namespaces

[hugobettmach]

Is your feature request related to a problem? Please describe.
Hi @DavidVujic, first of all this is such a great project, this way of organising python code makes so much sense in many situations.

The issue I came across is related to using multiple namespaces, under the top level namespace (or org_name) as mentioned in #45. This is something I think could be very useful for my use case.

But, when creating something like the example below...

├── README.md
├── bases
├── components
│   └── org_name
│       ├── namespace_1
│       │   ├── component_1
│       │   │   ├── __init__.py
│       │   │   └── core.py
│       │   ├── component_2
│       │   │   ├── __init__.py
│       │   │   └── core.py
│       │   └── component_3
│       │       ├── __init__.py
│       │       └── core.py
│       └── namespace_2
│           ├── component_1
│           │   ├── __init__.py
│           │   └── core.py
│           └── component_2
│               ├── __init__.py
│               └── core.py
├── development
├── poetry.lock
├── projects
├── pyproject.toml

Using poetry poly create component --name=namespace_1/component_1... And then running poetry poly info, I get:

Workspace summary

projects: 0
components: 2
bases: 0
development: 1

  brick                                                                       development
 ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
  namespace_1                                                                      -
  namespace_2                                                                      -

Describe the solution you'd like
Would be nice poly info could list all the components detected under "sub namespaces". Same would apply to bases as well. For example, would like a summary something like the one below. Hopefully this makes sense?

Workspace summary

projects: 0
components: 5
bases: 0
development: 1

  brick                                                                       development
 ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
  namespace_1                                                                      -
      component_1                                                                  -
      component_2                                                                  -
      component_3                                                                  -
  namespace_2                                                                      -
      component_1                                                                  -
      component_2                                                                  -

Additional context
Following on #45.

[DavidVujic]

Thank you, very interesting ideas @hugobettmach! Today the namespace_1 and namespace_2 are categorized as components by the poly tool, but I think it makes sense to support this kind of scenario too.