Time based configuration generalization

[aryanA101a]

@Userfrom1995

I have identified metrics_cache_max_age, blocking_timeout, rotate_frontend_password_timeout, max_connection_age, background_interval, authentication_timout, idle_timeout and log_rotation_age for them to use as_seconds to parse time and generalize their documentation.

[Userfrom1995]

@aryanA101a just look at my last PR #519 the only changes i have done related to this issue is removed as_logging_rotation_age() function to use as_seconds directly and also updated the documentation for metrics_cache_max_age and log_rotation_age .

[aryanA101a]

@jesperpedersen Should I go ahead with the above identified config params?

[jesperpedersen]

@aryanA101a Yes, go ahead

[aryanA101a]

@jesperpedersen as_seconds(...) expect unsigned int* as second arg and most of the config params I am migrating from as_int to as_seconds are int.

I believe these time config params should be unsigned. So do I proceed on changing them from int to unsigned int?

[jesperpedersen]

@aryanA101a Yes, you can do that