Handle local bitucket.properties file better

When a local bitbucket.properties file is used, the settings in the local version override the setting in the shared bitbucket.properties.

In a data center instance we need to have a stronger reaction if the database entry is found but doesn't match the database in the shared instance bitbucket.properties or if there are changes to the port we listen to, the proxies that we redirect to or any other changes that would cause the node to behave contradictory to the cluster.

Possible actions

• Prevent the node from starting with sufficiently descriptive message in the logs about why the node didn't start
• Ignore certain core settings like the Database and the proxies

There should also be a warning indicator in the GUI (similar to when you are not using the base url) when a local bitbucket.properties file is in use.