Multichain instances could expose all endpoints for all chains connected #1696
Description
Proposed Change or Idea
In the instances where more than one connection is specified (ie. RC and AH), we could implement a system where all the endpoints available in sidecar can be exposed for both the main connection (ie AH) and the secondary connection (ie RC) in such a way that the main connection would maintain the current endpoints denominations, while the secondary instance could have endpoints such as /rc/accounts/....
Additional Information
Some attention in doing so should be given to endpoints that require logic from both primary and secondary connections. One option could be to specify in the controller what connections are needed so on startup we can identify what endpoints to skip for this duplication