Fix bean field naming conflict in SpringServletXmlBeansConfiguration

[mortenrie]

In SpringServletXmlBeansConfiguration, two @Autowired fields had the same names as the @bean methods they were used in:

• globalClientSecretPolicy (field) clashed with globalClientSecretPolicy() (bean method)
• defaultClientSecretPolicy (field) clashed with defaultUaaClientSecretPolicy() (bean method)

This naming conflict is flagged by SonarQube as a code smell, since the field name shadows the method name within the same class, which can cause confusion and potential Spring wiring issues.

The fix renames the two injected fields to globalClientSecretPolicyConfig and defaultClientSecretPolicyConfig respectively, making them clearly distinct from the @bean factory methods and resolving the Sonar warning.

[linux-foundation-easycla]

• ❌ - login: @mortenrie / name: Morten Riedel . The commit (58f4ca1) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.