docs: refine API docs for files in Command dir

[devvaannsh]

The following changes are made:-

API Documentation Cleanup:
Removed all internal details from the API docs.
Now, only the exports.* content is included.

DefaultMenus.js Exclusion:
This file is internal, so it won’t show up in the API docs anymore.

Refactor in Menus.js:
The object literals inside MenuSection are now declared separately and assigned to the MenuSection object afterward.
This doesn’t affect any existing functionality.
The change was made because Docusaurus had trouble parsing nested object literals when generating markdown, which caused errors.

[devvaannsh]

The tests were failing because in file Menus.js, the variables were used before they were initialized! Fixed the issue!

[abose]

We need to add the following docs too:

• Commands.js - The well known exported command IDs needs to be in the docs somehow. maybe use enum?
• KeyBindingManager.js
• KeyboardOverlayMode.js
• Keys.js - maybe use enum?

Tracked in #1922

[devvaannsh]

In keybindingManager.js, the @private tags are placed after the function description. Why? Because the jsdoc-2-md library showed a warning that @private tags cannot have a description. So, if @private is defined above the description, it mistakenly treats the description as part of @private.

In keybindingManager.js, the @type tag for UN_SWALLOWED_EVENTS was changed from {(string)[]} to {Array.}, because the former format is invalid and throws an error.

In Commands.js, each export needs to be handled separately. JSDoc should be added for each export individually so that they show up correctly in the API docs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[abose]

LGTM. Thanks for contributing @devvaannsh