Add Network discovery/search by location (and time)

[sergiobrisio]

Problem description
While issues #86/#87 introduce an Areas discovery capability (with filters like atLocation, overlappingArea, coveringArea) that returns service areas and supported profiles, there is no analogous way to discover already‑instantiated Dedicated Networks by location and time window. Today, the DedicatedNetworks API supports:

• GET /networks → list all networks (no filters)
• GET /networks/{networkId} → read one network

Possible evolution
The proposal is to evaluate a couple of options:

• A (API‑local): Add discovery/search operations under DedicatedNetworks to filter existing networks by geo (and eventually expanding filters also to time or network status), maintaining the scope of Finding suitable areas where a reservable connectivity service can be provided #86/Areas API proposal #87 only for profile criteria.
• B (API‑shared): Extend the Areas Discovery from Finding suitable areas where a reservable connectivity service can be provided #86/Areas API proposal #87, so it can also return matching instantiated networks, not only NetworkProfiles or QoSProfiles.

[Masa8106]

Good proposal. I think enhancements of area discovery/serch function with some filtering option is good for API users.