Add API directory disclosure endpoint across all apps fed from some kind of registry - enables auto-discovery

[g8sun]

makes sense and was requested by @g8khan

[itadapter]

RE: #566 #567

The future path for service address discovery is to use metabase due to complex network resolution, however this ask is more about public service catalog for external consumers. If created, it should be called as SUCH "Public". Not sure if anything at all needed in Azos for this, and you should be building your system-specific endpoint which just reads a config file????

[g8sun]

We can use CMS to store API config file definitions for entering the root of the system. The CMS files are going to be read via an API server filter which the caller can transact by passing parameters such as: env, network, binding(addressing mode), pub/pvt visibility, category, release date etc...

So basically CMS will store proprietary database definition files (config files) which server controller will filter using LINQ.

We need to think how to integrate this with API doc for better auto-discovery of endpoints, so we would not need to re-list all endpoints every time

[g8sun]

This Is a PROJECT, not a feature; this is probably a 2022 Q1 item after IDP which is more needed for MVP as of today.