Add v1 API support for legacy operations

[anjor]

Description

The foundry-platform-python SDK provides both v1 and v2 APIs. While the CLI currently focuses on v2 operations, some organizations may still require v1 compatibility for legacy operations that haven't been migrated to v2.

Use Cases

• Organizations with existing v1 integrations
• Operations that are only available in v1 API
• Gradual migration from v1 to v2

Implementation Considerations

• Add a flag or configuration option to specify API version (e.g., --api-version v1)
• Create v1-specific service implementations where needed
• Maintain backward compatibility while defaulting to v2
• Document which operations are v1-only vs v2-only

Affected Modules

Based on SDK documentation, v1 APIs exist for:

• Core/models
• Datasets
• Ontologies

Implementation Approach

1. Add version configuration to the base service class
2. Create v1 service variants where necessary
3. Add command-line flags for version selection
4. Update documentation to clarify version support

References

• SDK v1 docs: https://github.com/palantir/foundry-platform-python/tree/develop/docs/v1
• SDK v2 docs: https://github.com/palantir/foundry-platform-python/tree/develop/docs/v2