capture database frozen state in the support zip

Databases are frozen by the Export Configuration task or possibly something else like a groovy script. During that time a support zip may be generated. It is important for support to know if any of the 6 databases are frozen as that may help us determine this as a cause to a reported problem.

Currently there is a frozen.marker file written to the db directory which could contain some relevant info. It may be prudent to capture that file in the support zip if present. Alternately you could store the database frozen state inside jmx.json ( from an mbean ) or sysinfo.json as a datapoint.