Updating the mule-artifact.json with minimumMuleVersion as 4.6.0 causes the custom policy deployment to fail

A custom policy which contains an http request and was created in 4.3.0 or before will fail to be deployed with the following error on 4.4.0 and above when the customer modifies the minimum mule version in mule-artifact.json from 4.3.0 to above 4.4.0.

org.xml.sax.SAXException: Can't resolve http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd, A dependency or plugin might be missing

The issue occurs because the custom policy POM contains the below and the feature mule.enable.policy.isolation introduced in 4.4.0 together cause the issue.

<dependency>
<groupId>com.mulesoft.anypoint</groupId>
<artifactId>mule-http-policy-transform-extension</artifactId>
<version>${http.policy.transform.extension}</version>
<classifier>mule-plugin</classifier>
<!— HTTP Connector is excluded to avoid packaging it with the policy, since the application's HTTP connector is used-->
<exclusions>
<exclusion>
<groupId>org.mule.connectors</groupId>
<artifactId>mule-http-connector</artifactId>
</exclusion>
</exclusions>
</dependency>