TransCompressionCommand Inoperable

`TransCompressionCommand` in parquet-tools is intended to allow translation of compression types in parquet files.  We are intending to use this functionality to debug a corrupted file, but this command fails to run at the moment entirely. 

Running the following command (on the uncorrupted file):
```java

java -jar ./parquet-tools-1.11.1.jar trans-compression ~/Downloads/part-00048-69f65188-94b5-4772-8906-5c78989240b5_00048.c000.snappy.parquet
```
This results in 

 
```java

Unknown command: trans-compression
```
 

I believe this is due to the Registry class [silently catching any errors to initialize](https://github.com/apache/parquet-mr/blob/master/parquet-tools/src/main/java/org/apache/parquet/tools/command/Registry.java#L65) which subsequently is [misinterpreted as an unknown command](https://github.com/apache/parquet-mr/blob/master/parquet-tools/src/main/java/org/apache/parquet/tools/Main.java#L200).

We need to: 
1. Write a test for the TransCompressionCommand to figure out why it's showing up as unknown command
1. Probably expand these tests to cover all the other commands

 

This will then unblock our debugging work on the suspect file. 

**Environment**: I am using parquet-tools 1.11.1 on a Mac machine running Catalina, and my parquet-tools jar was downloaded from Maven Central. 
**Reporter**: [Shelby Vanhooser](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vanhooser)

_{**Note**: *This issue was originally created as [PARQUET-1948](https://issues.apache.org/jira/browse/PARQUET-1948). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*}

Commencez dans parquet-tools/src/main/java/org/apache/parquet/tools/command/Registry.java et org/apache/parquet/tools/Main.java, puis exécutez la commande trans-compression signalée afin de reproduire le résultat unknown-command. Ajoutez un test pour TransCompressionCommand et étendez la couverture aux autres commandes si applicable ; le travail est considéré comme terminé lorsque la commande est reconnue et que les tests expliquent pourquoi elle échouait auparavant.

Rédigé par le modèle d'indexation à partir du texte de l'issue.