微信支付:默认使用公钥模式，全部v3接口添加Wechatpay-Serial请求头

[buaazyl]

1. 默认使用公钥模式
2. 全部v3接口添加Wechatpay-Serial请求头
3. 调整apiV3秘钥命名
4. 更新了readme中v2、v3新版文档地址

[augmentcode]

🤖 Augment PR Summary

Summary: This PR updates WxJava WeChat Pay (v3) defaults and configuration naming to better align with the newer public-key flow and request header requirements.

Changes:

• Rename API v3 key property from apiv3Key/apiv3-key to apiV3Key/api-v3-key in Spring Boot starters
• Default-enable “add Wechatpay-Serial header for all v3 requests” and “full public key mode” in starter properties
• Wire the renamed property through auto-configuration/multi-service builders and update the related unit test
• Refresh README references for WeChat Pay v2/v3 documentation URLs

Technical Notes: Spring Boot relaxed binding will now expect api-v3-key (or apiV3Key in YAML) for v3 key configuration; defaults differ depending on whether users construct WxPayConfig directly or rely on starter properties.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

Renaming apiv3Key to apiV3Key is a breaking change for configuration binding: existing configs using wx.pay.apiv3-key will no longer populate this field and can fail at runtime with a missing API v3 key. If upgrades need to be smoother, consider whether a compatibility path (accepting both names) is required.

Severity: high

Other Locations

• spring-boot-starters/wx-java-pay-multi-spring-boot-starter/src/main/java/com/binarywang/spring/starter/wxjava/pay/properties/WxPaySingleProperties.java:61

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[buaazyl]

starter配置和本体使用的配置项命名应该保持一致