Revert "added limitations on metadata web billing (#932)" (#937)

This reverts commit 6d4926c.

Author: antoniobg

docs/web/web-billing/custom-metadata.mdx

@@ -59,10 +59,6 @@ You can see how to use the webhook integration to trigger automations and workfl
 
 ![](/docs_images/web/web-billing/metadata-in-initial-purchase-event.png)
 
-## Limitations
-
-Currently, metadata is only supported for subscription purchases (`INITIAL_PURCHASE` webhook events). Metadata is **not supported** for one-time purchases (`NON_RENEWING_PURCHASE` webhook events). This means that custom metadata and UTM parameters sent with one-time purchases will not be propagated to webhook events or the Stripe customer object.
-
 ## Opt out of the automatic collection of UTM parameters
 
 You can opt-out of the automatic collection of UTM parameters in the Web SDK by setting the `autoCollectUTMAsMetadata` flag to `false` in the `configure` method.

docs/web/web-billing/overview.mdx

@@ -62,7 +62,6 @@ Web Billing currently has a few limitations:
 - There is no support for RevenueCat's Paywall templates (coming soon).
 - There is no support for translated content in customer emails (these are currently only sent in English, regardless of the selected locale).
 - We do not collect and store the customer's name, shipping address or full billing address. Consequently, Web Billing cannot currently be used in India and in other countries that have this requirement.
-- Custom metadata is only supported for subscription purchases (`INITIAL_PURCHASE` events) and not for one-time purchases (`NON_RENEWING_PURCHASE` events). See [Custom Metadata](custom-metadata#limitations) for more details.
 
 ### Stripe Billing integration