feat: restrict explorer new-item menu to folders-only at org level

[kptdobe]

Summary

Customer reported they cannot edit a sheet created at the org level (da-admin cannot read the sheet). 2 solutions: fix da-admin or simply restrict the UI to only allow folder creation at the org level. This is implementing the latter.

• At the org level (path depth 1 — e.g. #/org), clicking New skips the type-picker dropdown and jumps straight to the folder name input, since the only valid thing to create there is a site/folder
• At site level and deeper (#/org/site/...) the full menu (Folder, Document, Sheet, Media, Link) is preserved unchanged
• Implemented via a new folderOnly boolean prop on da-new; da-browse derives the value from the existing isRootFolder() helper

Test plan

• Navigate to an org (#/org) — click New, verify it goes directly to the name input with no dropdown
• Navigate to a site (#/org/site) — click New, verify the full Folder/Document/Sheet/Media/Link menu appears
• Create a folder from the org level and confirm it appears in the list
• npm test passes (1454 tests, all green)

🤖 Generated with Claude Code

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

• Re-sync branch

Commits

• a29d0f7 ❌ (latest)