Hub cli

[CalebCourier]

Summary

This PR adds the following commands to the guardrails cli for hub support:

• guardrails configure
• guardrails hub install

It also refactors cli.py into a directory for better maintainability as we add more cli commands.

Behaviour of guardrails hub install

In order to prevent namespace collisions, the install subcommand will do the following with validator modules during installation:

1. Create a namespace directory for the validator's authoring organization if one does not exist
2. Create a directory under the above named after the package name defined in the manifest
3. Use pip to install the validator module without any dependencies into the package directory from step 2
4. Use pip to inspect the package directory to determine dependencies for this validator
5. Install those dependencies in the active site-packages directory from the sys environment
6. Adds entries to the init files in guardrails.hub and guardrails.hub.{namespace}

Step 5 means that common dependencies will be re-used across validator modules. This means that conflicting dependency versions can be an issue like every other python environment.

Depends On

#530

[CalebCourier]

I didn't write tests for anything under hub/server because that will all be moving to the proxy server this week and likely won't be in python anymore.

[notion-workspace]

CLI

[notion-workspace]

Split install script to server/client

[notion-workspace]

CLI opt-out