remote nexus studio repository proxies requests cpu loading

Customers may use their own artifacts repository server (nexus) and declare the studio repository as a proxy. This could generate from the server a lot of requests for having a state about artifacts which are not studio projects.

These requests are managed by our maven servlet. At this time, all requests are processed in the same way which involve a query in the database about the artifact. This can easily overload the system and should be avoided. We should think about protecting the application for the resources involved in that request processing.

The first idea is to reject immediately requests that do not concern hosted studio artifacts. We could solve that concern by having a cache in place where we will be able to state about the artifact requested (as the repository servers do).