[Feature]: `dirctl validate` for client-side record validation

[akijakya]

Problem Statement

There is no way other than using the MCP server to validate a record locally before pushing.

It would also be valuable if the whole directory could be re-validated with a dirctl validate command, ensuring the node's content is compatible with

• another OASF instance
• the JSON schema validator
• the currently used OASF instance that added new validation rules/fixed existing ones

Proposed Solution

Implement a validate command with flags

• to provide a schema url
• disable strict API validation
• disable API validation so the schema validator would be used
• specify a server instance for a content re-validation
• pass a record json that would be validated locally

Alternatives Considered

No response

Additional Context

No response

Checklist

• I have read the contributing guidelines
• I have verified this does not duplicate an existing feature request