Revamp documentation to prioritize Java/Annotation-Based configuration over XML

[salmar]

The current reference documentation shows XML configuration as the primary configuration style in some sections. While XML is still supported, it has not been the mainstream choice for more than a decade. XML examples can make the framework feel outdated and newcomers may get the wrong impression that XML is still recommended.

It would be helpful to reframe the introduction of configuration approaches in the The IoC Container section to align the documentation with the current Spring usages and show Java/Annotation-Based configuration first.

Also, examples in sections like: Resources, Validation, Data Binding, and Type Conversion, Transaction Management, Initializing a DataSource, Object Relational Mapping (ORM) Data Access, Marshalling XML by Using Object-XML Mappers, Locale, View Technologies could show default examples in Java-config and keep the XML equivalent in a hidden secondary tab for reference.