Feature Policy: remove payment tests (#58212)

Author: marcoscaceres

feature-policy/README.md

@@ -37,8 +37,8 @@ HTTP tests are used to test features with header policy.
 * test if feature is enabled / disabled in a cross-origin iframe.
 
 Examples:
-`/feature-policy/payment-disabled-by-feature-policy.https.sub.html`
-`/feature-policy/payment-disabled-by-feature-policy.https.sub.html.headers`
+`/feature-policy/feature-disabled-by-feature-policy.https.sub.html`
+`/feature-policy/feature-disabled-by-feature-policy.https.sub.html.headers`
 
 ### How to Write Container Policy Tests
 Simply use `test_feature_availability()` with the optional argument
@@ -47,13 +47,13 @@ Simply use `test_feature_availability()` with the optional argument
 * feature is enabled / disabled in a cross-origin iframe.
 
 Example:
-`/feature-policy/payment-allowed-by-feature-policy-attribute.https.sub.html`
+`/feature-policy/feature-allowed-by-feature-policy-attribute.https.sub.html`
 
 ### How to Write Container Policy Tests with Redirect
 Similar to the section above, append
 `/feature-policy/resources/redirect-on-load.html#` to the argument `src`
 passed to `test_feature_availability()`.
 
 Example:
-`/feature-policy/payment-allowed-by-feature-policy-attribute-redirect-on-load.https.sub.html`
+`/feature-policy/feature-allowed-by-feature-policy-attribute-redirect-on-load.https.sub.html`