Test content database properties not set

[dmcassel]

Describe the bug
When I run mlDeploy (or mlDeployDatabases or mlUpdateIndexes), the content database is deployed correctly but the call to set the properties on the test content database is not made. As a result, the test database is missing indexes, causing tests to fail.

I figured out this was due to a little non-standard configuration (old project), which is why it hasn't been a problem for other projects. On this project:

• the name of the content database definition file was {mlAppName}-content.json.
• in the content database definition file, we had: "database-name": "%%mlAppName%%-content",

I changed them to the standard:

• content-database.json
• "database-name": "%%DATABASE%%",

and it worked again. Seems odd as I thought they would be equivalent, but at least it's simple to resolve.

To Reproduce
Steps to reproduce the behavior:

1. Set up the content database definition as described above. Make sure there's at least one index or something non-standard.
2. Run mlDeploy or mlDeployDatabases
3. Observe that the call to update the test content properties is not sent

Expected behavior
I had thought that the differences above would not be a problem. This could be resolved either through code (making ml-gradle work with that configuration) or documentation. Easy to work around, so I wouldn't give it high priority.