Improve Docs

[zllkjc]

1. We should classify more content by scenario. Like SSR、AssetPrefix、Compatibility....
2. The document should have a clear classification of APIs, such as what version to start supporting, which APIs are experimental, and which are ready to be deprecated.
3. document should be correctly.
4. if some features are recommended for community implementation, use cases should be clearly listed

[zllkjc]

#5154 #5306

[zllkjc]

#3680

[zllkjc]

#5175

[zllkjc]

#5276

[zllkjc]

#3353

[zllkjc]

Unit Test use case.

[chenjiahan]

• Add more Rsbuild new build config to Modern.js document, and link to Rsbuild document for detailed information.
• Mark the deprecated Rsbuild config and provide some migration tips.

@9aoy cc

[zllkjc]

• Remove global Proxy in Modern.js docs
• provide some community use case for proxy ?

[zllkjc]

• JSX document add inline script use case
• Do we need ESLint docs ?

[zllkjc]

• remove Hooks in Modern.js

[zllkjc]

• Do we need Reduck or generator in Modern.js docs

[zllkjc]

• intergate SSR/SSG/CSR to rendering ?
• intergate Entry to Routing with convention routes ?
• CSS Module is better in Style ?
• Add follow sections into 'Optimization' ? (rsbuild docs is already do)
  
  also code split
• Add debug for proxy / mock / inspect command ...