validity check error when loading all records from a custom records.yaml

[brbzull0]

Was doing some tests and I found the following errors, need further investigation on this.

[Aug  5 15:21:05.918] traffic_server NOTE: Warn:   Warn: proxy.config.diags.logfile.rolling_min_count - Validity Check failed. '^0*[1-9][0-9]*$' against '0'. Default value will be used
  Warn: proxy.config.http2.default_buffer_water_mark - Validity Check failed. '^[0-9]+$' against '-1'. Default value will be used
  Warn: proxy.config.log.rolling_min_count - Validity Check failed. '^0*[1-9][0-9]*$' against '0'. Default value will be used
  Warn: proxy.config.net.additional_accepts - Validity Check failed. '^-1|[0-9]+$' against '-1'. Default value will be used
  Warn: proxy.config.output.logfile.rolling_min_count - Validity Check failed. '^0*[1-9][0-9]*$' against '0'. Default value will be used
  Warn: proxy.config.ssl.client.version.max - Validity Check failed. '^-?[0-9]+$' against '-1'. Default value will be used
  Warn: proxy.config.ssl.client.version.min - Validity Check failed. '^-?[0-9]+$' against '-1'. Default value will be used
  Warn: proxy.config.ssl.server.version.max - Validity Check failed. '^-?[0-9]+$' against '-1'. Default value will be used
  Warn: proxy.config.ssl.server.version.min - Validity Check failed. '^-?[0-9]+$' against '-1'. Default value will be used

[brbzull0]

It seems we do not run the validation when loading the default configuration from RecordsConfig.cc, once this is clear it may be a good idea to run this to avoid further mismatches between types, values and validation.