Add ability to suppress the automatic promotion of non-durable queues to durable during automated store upgrade

QPID-3913 introduced the ability for the Java Broker to automatically upgrade bdb-stores that were created by earlier versions of the Broker (rather than having to run the separate bin/storeUpgrade.sh tool).

In this change, the user lost the the ability to control how the broker handles the existence of persistent messages on non-durable queues. Currently, the Broker always promotes these queues to durable so that the messages may be recovered. The user has no ability to override this behaviour. Additionally, the fact that a durable queue has been created is not recorded in the log.

We should consider:

• logging the fact that a non-durable queue has been promoted to durable by the auto upgrade process
• allow this behaviour to be suppressed.