Prevent errors when calling HandleConsentRequest a second time

[kminehart]

Signed-off-by: Kevin Minehart [email protected]

Related issue

#1256

Previous PR: #1301

Proposed changes

If HandleConsentRequest is called a second time, then:

• If the request was not used (was_used = false), then the old ConsentRequest is replaced with the newly provided data.
• If the request was used (was_used = true), then the old ConsentRequest is returned, whereas previously a SQL error would be returned.

Checklist

• I have read the contributing guidelines
• [ x 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 signed the Developer's Certificate of Origin
  by signing my commit(s). You can amend your signature to the most recent commit by using git commit --amend -s. If you
  amend the commit, you might need to force push using git push --force HEAD:<branch>. Please be very careful when using
  force push.
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation within the code base (if appropriate)
• I have documented my changes in the developer guide (if appropriate)

Further comments

Sorry about messing up the old PR! I tried something new with squashing commits but that backfired when I forgot to sign an older commit. 🤷‍♂️

[aeneasr]

Nice, thank you :)