Docs(Plugins): Synchronize plugin documentation with the main volcano repository

[JesseStutler]

Goal

Add missing plugin documentation to the website to align with the plugins available in the volcano-sh/volcano repository.

Context

The website documentation is missing several plugins that exist in the main Volcano repository. This task is to identify the missing plugins and create their corresponding documentation pages.

• ResourceStrategyFit
• capacity
• proportion
• deviceshare
• extender
• network-topology-aware
• nodegroup
• sla
• usage
• resourcequota

Acceptance Criteria

• A list of plugins present in the volcano-sh/volcano repository but missing from the volcano-sh/website documentation is created.
• For each missing plugin, a new documentation file is created under the content/en/docs/plugins/ directory.
• The new documentation accurately describes the functionality of each plugin.

[JesseStutler]

/help
/kind documentation

[volcano-sh-bot]

@JesseStutler:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

/help
/kind documentation

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[HeyCamCam]

/assign

[HeyCamCam]

I compared what I found in the volcano/pkg/scheduler/plugins directory to the contents of the website/content/en/docs/plugins.md file. I added the missing plugins to the plugins.md file as I wasn't sure if you truly wanted a new subdirectory called "plugins". I would need further assistance for each plugins overview and scenario statements as I don't want to insert inaccurate assumptions.

[JesseStutler]

I compared what I found in the volcano/pkg/scheduler/plugins directory to the contents of the website/content/en/docs/plugins.md file. I added the missing plugins to the plugins.md file as I wasn't sure if you truly wanted a new subdirectory called "plugins". I would need further assistance for each plugins overview and scenario statements as I don't want to insert inaccurate assumptions.

@HeyCamCam Thank you for your assignment, I hope to refactor Plugins to subdirectory(or called submenu under scheduler): #425, but I'm not familiar with frontend development and also copilot can not handle it, so I hope someone with familiar with frontend development could refactor first and then add each plugins' docs under Plugins subdirectory. Otherwise the current plugin.md may become very big and hard to search and read. But the content you written will still be very useful.