FluoConfiguration should derive table name from application name if not set

FluoConfiguration requires the application name to be set. However, it does not require the table name to be set (defaults to "fluo"). Problems can occur if separate applications use the same table. The table name should be derived from the application name, if not explicitly set. Or, the table name should be required.

Additionally, the configuration should have more javadocs explaining what the application name is used for, and how it relates to the table name, and explaining the pitfalls of using the same table for different applications.

Start with the FluoConfiguration class and trace how the application name and default table name are currently handled. Resolve whether the table name should be derived or required, then update the configuration behavior and add the requested Javadocs explaining their relationship and the risks of sharing a table.

Written by the indexing model from the issue text.