fix: improve resolver error messages with specific failure context

[JoshSalway]

Summary

• Replace generic "Unable to resolve X" error messages across all 16 resolvers with specific, actionable messages that distinguish between: ID not found, name not found, no identifier provided, and (for ApplicationResolver) repository not matched
• Improve the base Resolver::resolveFromIdentifier() to catch Saloon\Exceptions\Request\RequestException specifically — 404s fall through to name-based lookup, while 403 (permission) and other HTTP errors are re-thrown with context instead of being silently swallowed
• Add looksLikeId() helper to the base Resolver, reused by all subclasses to tailor error messages based on whether the user provided an ID or a name

Before

Unable to resolve application: my-app
Unable to resolve environment: env-abc123

After

No application named 'my-app' found in your organization.
Environment 'env-abc123' not found. Verify the ID is correct and belongs to your application.
No application found matching repository 'user/repo'. Create one or provide an application ID or name as an argument.

Closes #30

Test plan

• All existing tests pass (./vendor/bin/pest — 31 passed)
• PHPStan analysis passes with no errors on app/Resolvers/
• Manual: run cloud app:info bad-name and verify "No application named 'bad-name' found" message
• Manual: run cloud app:info app-nonexistent123 and verify "Application 'app-nonexistent123' not found" message
• Manual: run cloud env:info from a non-linked repo and verify repo-specific or generic fallback message

🤖 Generated with Claude Code