fix(db-manager): set health check and conn_max_age to 1 hour

[jfagoagas]

Context

Django is revoking connections with the following exception: django.db.utils.InterfaceError: connection already closed

Description

• Configure CONN_MAX_AGE for an hour instead of 0 which automatically closes the connection.

Checklist

• Are there new checks included in this PR? Yes / No
  • If so, do we need to update permissions for the provider? Please review this carefully.
• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.90%. Comparing base (d8fc830) to head (7f9b8e7).
Report is 43 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6088      +/-   ##
==========================================
+ Coverage   89.93%   92.90%   +2.96%     
==========================================
  Files        1147       59    -1088     
  Lines       35611     5102   -30509     
==========================================
- Hits        32028     4740   -27288     
+ Misses       3583      362    -3221     

Flag	Coverage Δ
api	92.90% <ø> (?)
prowler	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
prowler	∅ <ø> (∅)
api	92.90% <ø> (∅)

[jfagoagas]

Closing this since the issue was not introduced by Django.