New symbol for defining the path to the component dependencies file

When first implemented in 5.8.3, the file was hardwired to tapestryComponentDependencies.json in the folder where the JVM is ran. This can be a limitation if you're running more than webapp in the same servlet container and, of course, it's nice to have it configurable.

This ticket introduces a new configuration symbol, tapestry.component-dependency-file (SymbolConstants.COMPONENT_DEPENDENCY_FILE), with a default value of tapestryComponentDependencies.json to keep the existing behavior, which accepts a path that can be either absolute or relative to the folder where the JVM is running.

In addition, this ticket adds logging about reading and writing the component dependency file and tweaks PageCatalog a bit regarding what to show when production mode is off.