WIP: Initial crypto POC

### Playing around with some AES encryption. 
Very much still WIP but wanted to toss it up to get some feedback on structure, etc. Currently not using named parameters, but that is our goal going forward.

**Don't forget to modify your gopath per the readme and run `go build` before testing**

Hopefully you should be able to follow the `-h` help menus for the commands to figure out how they work.

Right now everything just goes to STDOUT. Piping is supported so you can do crazy things like this:

```
echo -n "Some secure secret" | ./secrets create-secret name 5zEMDovHlgztnYN42fVQjnnhUzbEEpThKHgu5kZ9fRo=
```

or 

```
cat README.md | ./secrets create-secret name 5zEMDovHlgztnYN42fVQjnnhUzbEEpThKHgu5kZ9fRo= | ./secrets read-secret name 5zEMDovHlgztnYN42fVQjnnhUzbEEpThKHgu5kZ9fRo=
```
*Currently the secret name is completely unused, but a hashing function to generate the value we'll send to the server is in place, it's just not being called or written to STDOUT at the moment, it should still be reviewed.*

Before playing around generate a valid encryption token with `./secrets generate-token`. The length of the encryption token enforces AES256.

Very rudimentary tests have been setup in the command directory so you can run `go test ./command` (use the `-v` option for verbose output).

 
Yes this is the encryption token. So the issue here is that the key needs to be exactly 32 bytes (256 bits) in order for AES256 to work, if we move off of AES, or somehow mess with a given key to jam it down to 32 bytes then maybe we could use some arbitrary value, though IMO we should stick with something generated to ensure high quality tokens.