[docs-scanner] Unclear deprecation status and migration path for Compose standalone

[docker-agent]

File: content/manuals/compose/install/standalone.md

Issue

The page warns that standalone installation is "not recommended and is only supported for backward compatibility purposes" but provides detailed installation instructions without explaining:

• Why it's not recommended
• What users should use instead (beyond the vague "not recommended")
• Whether this will be removed in the future
• How to migrate away from standalone

The warning appears twice:

This install scenario is not recommended and is only supported for backward compatibility purposes.

But the page then provides complete, current installation instructions for both Linux and Windows Server, suggesting it's still a viable option. This creates confusion about whether users should avoid this entirely or if it's acceptable for certain use cases.

Suggested fix

Either:

1. Add a clear deprecation notice with timeline if this will be removed, and provide migration instructions
2. Or, if this is genuinely supported for backward compatibility indefinitely, explain when users should use this (e.g., "Use standalone only if you cannot use Docker Desktop or the plugin for specific technical reasons") and clarify the limitations/risks
3. Or, if this should not be used at all, remove the detailed instructions and replace with a brief notice pointing to the recommended installation methods

The current state leaves users uncertain whether they should follow these instructions or avoid them entirely.

---

Found by nightly documentation freshness scanner