feat: extend latest and session related consents

[aarmam]

This pull request introduces feature to extend consent validity time for both session related consent and subject related consent. Currently consent validity cannot be updated (when skip=true) or to be more precise - consent updates only if new device/browser accepts consent.

Checklist

• I have read the contributing guidelines.
• I have referenced an issue containing the design document if my change
  introduces a new feature.
• I am following the
  contributing code guidelines.
• I have read the security policy.
• I confirm that this pull request does not address a security
  vulnerability. If this pull request addresses a security. vulnerability, I
  confirm that I got green light (please contact
  [email protected]) from the maintainers to push
  the changes.
• I have added tests that prove my fix is effective or that my feature
  works.
• I have added or changed the documentation.

[codecov]

Codecov Report

Merging #3043 (313256f) into master (3b1d87e) will increase coverage by 0.31%.
The diff coverage is 92.65%.

❗ Current head 313256f differs from pull request most recent head e6963be. Consider uploading reports for the commit e6963be to get more accurate results

@@            Coverage Diff             @@
##           master    #3043      +/-   ##
==========================================
+ Coverage   76.85%   77.16%   +0.31%     
==========================================
  Files         124      124              
  Lines        9162     9348     +186     
==========================================
+ Hits         7041     7213     +172     
- Misses       1672     1680       +8     
- Partials      449      455       +6     

Impacted Files	Coverage Δ
consent/manager.go	100.00% <ø> (ø)
consent/handler.go	66.45% <50.00%> (-0.32%)	⬇️
persistence/sql/persister_consent.go	86.98% <83.87%> (-0.44%)	⬇️
consent/manager_test_helpers.go	98.18% <100.00%> (+0.25%)	⬆️

... and 1 file with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[aeneasr]

Can you please make this PR against the #2796 branch as we have done quite a lot of work on the DB layer and don't want to backport new changes to it as it has grown in scope significantly already. Thank you :)