[Bug]: Behavioral Differences in MI 4.2.0 vs. MI 4.3.0 with the Use of '-DenablePrometheusApi' Property.

[SameeraSI]

Description

In MI 4.2.0.104 and MI 4.3.0.3, there are differences in API request routing behavior when using the -DenablePrometheusApi=true or -DenablePrometheusApi=false flags to start the server.

For example, if there are two APIs with the contexts /materials and /materials/1.1 (with the version defined in the context, e.g., <api context="/materials/1.1" name="materialsAPI" xmlns="http://ws.apache.org/ns/synapse">), in MI 4.2.0, the following cURL command:
curl --location 'https://localhost:8253/materials/1.1'
will correctly route to the API with the context /materials/1.1. However, in MI 4.3.0, the same cURL command will incorrectly route to the API with the context /materials.

This issue can also appear inversely between MI 4.3.0 and MI 4.2.0 when API versions are defined separately, for example:
<api context="/materials" name="materialsAPI" version="1.1" version-type="url" xmlns="http://ws.apache.org/ns/synapse">
In this case, the routing behavior may differ across versions.