Undesired behaviour in Istio Adapter integration option in Admin Portal

When using the service mesh integration and creating a new mapping rule, those rules do not get pushed into the proxy configuration which the adapter relies on.

The service mesh integration option should automatically update the proxy config and push to production or else we need to think of an alternative.

The 3scale istio adapter uses the "Proxy Config Show Latest - GET" endpoint in the Account Management API. It passes the "environment" key with a value of "production" as a query parameter.

Therefore, the adapter expects that each time a new mapping rule is created under an API that uses the "Istio Integration" option, then clicking the update should automatically update that proxy config and push it to production.

Update Feb. 8th:

• Discussed and agreed that in the UI the changes will be saved in staging and be pushed to prod.
• Discussed and agreed that if making changes via API will require to make changes in staging and then use different endpoint to push changes to prod. We discussed not needing to specify the environment (production) and just using default if no value (customers of the adapter won't necessarily know about staging and production and we decided not to introduce that at this point).

The priority here is to fix the bug, even if that means the mapping rules are a bit hidden for a while. For that, see https://issues.jboss.org/browse/THREESCALE-1689 and its subtasks.