Workspace command suite issues

## Bug Report

Using one issue for a whole list of bugs/missing QoL issues that can be fixed in one go.

- No standards support in `add` or `new` commands
- No way to use workspaces from a folder that isn't a git repo without a fake .git - need to default looking in current directory if no .git found.
- Add puts the full absolute path to the file into the workspace. This is practically useless. You should either resolve a relative path from the workspace file, or have every path be relative to the workspace root (preferred).
- `rm` makes you specify the english name of the thing to delete. This should probably take the $id, but users will want to use an interactive flow - so add inquirer support
- Templates for `new` are using a very old CALM core schema.