feat(core): Add two new queries (shop-api) to get public payment and shipping methods

[apoca]

Description

I propose adding two public GraphQL queries in the Vendure core:

1.	activePaymentMethods – Returns a list of all active PaymentMethods.
2.	activeShippingMethods – Returns a list of all active ShippingMethods.

These queries would allow frontend developers to dynamically fetch and display the current active methods without requiring access to the cart or checkout state. This would ensure consistency between the backend configuration and the frontend display, reducing the need for manual intervention when changes are made.

query activePaymentMethods {
  activePaymentMethods {
      id
      name
      code
      description
      translations {
        id
	languageCode
        name
        description
      }
    }
}

query activeShippingMethods {
  activeShippingMethods {
      id
      name
      code
      description
      translations {
        id
	languageCode
        name
        description
      }
    }
}

issue: #3312

Breaking changes

n/a

Screenshots

n/a

Checklist

📌 Always:

• I have set a clear title
• My PR is small and contains a single feature
• I have checked my own PR

👍 Most of the time:

• I have added or updated test cases
• I have updated the README if needed

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Jan 20, 2025 4:10pm

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[apoca]

I have read the CLA Document and I hereby sign the CLA

[apoca]

@michaelbromley, another thing, I think that both the payment method and the shipping method could have an associated asset (image), so we could use the brand logos... What we will do if this is not possible on the Vendure part is to use the customField for this. , but it honestly doesn't feel right to me.