Doc Improvements: Monetizing an API

Description

• As a fresh starter, I was trying to activate the Stripe account which is the sample billing engine we use in this doc, and the activation process is very hard. But it is not needed when we use it in a test mode.
  Hence it is better to mention that we do not need an activated account for testing.

• Stripe UI has been changed
  Screen shots need to be changed for Stripe UIs in [1].

• org.wso2.apim.monetization.impl-1.3.0.jar is the latest version support for the current latest APIM version (4.1.0).
  This should be updated in 1. Connect WSO2 API Manager to the billing engine. in [2]

• Format and Example of c. Define the Access Token required to access the above Query API. has two '='s.

[apim.monetization]
analytics_access_token = "<Token to access the Choreo query API>"

[apim.monetization]
analytics_access_token = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

• We should mention Update/Replace in a. Enable analytics. under 4. Optionally, configure WSO2 API Manager to work with Choreo Analytics.. Otherwise, users will tend to add a separate entry and it causes to produce conflicts and errors when starting the server.

• Screenshots provided in [3] & [4] are too small and cannot be opened in full screen.

Location: https://apim.docs.wso2.com/en/4.1.0/design/api-monetization/monetizing-an-api/

[1] https://apim.docs.wso2.com/en/4.1.0/design/api-monetization/monetizing-an-api/#a-configure-the-billing-engine
[2] https://apim.docs.wso2.com/en/4.1.0/design/api-monetization/monetizing-an-api/#b-configure-wso2-api-manager
[3] https://apim.docs.wso2.com/en/4.1.0/design/api-monetization/monetizing-an-api/#step-1-create-a-subscription-polic
[4] https://apim.docs.wso2.com/en/4.1.0/design/api-monetization/monetizing-an-api/#step-2-enable-monetization