Operation policy feature change should be reflected in threat protection setup

Description:
With the introduction of operational policies, previous approach of applying sequences is changed from APIM 4.1.0 onwards. All 3 types of threat protection should be done using "Policies" view of an APIM publisher instead of using "Runtime" view.

• #5879
  : https://apim.docs.wso2.com/en/latest/design/api-security/threat-protection/gateway-threat-protectors/gateway-threat-protectors-for-api-manager/#add-a-custom-sequence
• #5875
  : https://apim.docs.wso2.com/en/4.1.0/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/regular-expression-threat-protection-for-api-gateway/
• #5877
  : https://apim.docs.wso2.com/en/4.1.0/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/json-threat-protection-for-api-gateway/
• #5878
  : https://apim.docs.wso2.com/en/4.1.0/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/xml-threat-protection-for-api-gateway/

Affected Product Version:
APIM 4.1.0 and master docs

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Review the four linked APIM threat-protection pages, starting with the custom-sequence page and the APIM 4.1.0 threat-protection instructions. Update each workflow to use the publisher's Policies view rather than Runtime; done when custom-sequence, regex, JSON, and XML threat protection instructions reflect the operational-policy approach.