Ducktape solutions for #3585

[originalsouth]

Changes

Ducktape solutions for #3585

This patch:

• reverts 1b4aed6
• implements a the "Make ε bigger and hope the situation converges" remedy as mentioned in Data inconsistencies in Octopoes: a proposal to retire celery and validate the model continuously  #3585 (comment)

Issue link

#3585

Demo

N/A

QA notes

• All affirmations should not be pending in a steady state
• In VisualOctopoesStudio++ there should not be a any dangling objects

---

Code Checklist

• All the commits in this PR are properly PGP-signed and verified.
• This PR only contains functionality relevant to the issue.
• I have written unit tests for the changes or fixes I made.
• I have checked the documentation and made changes where necessary.
• I have performed a self-review of my code and refactored it to the best of my abilities.

• Tickets have been created for newly discovered issues (see Data inconsistencies in Octopoes: a proposal to retire celery and validate the model continuously  #3585).
• For any non-trivial functionality, I have added integration and/or end-to-end tests.
• I have informed others of any required .env changes files if required and changed the .env-dist accordingly.
• I have included comments in the code to elaborate on what is not self-evident from the code itself, including references to issues and discussions online, or implicit behavior of an interface.

---

Checklist for code reviewers:

Copy-paste the checklist from the docs/source/templates folder into your comment.

---

Checklist for QA:

Copy-paste the checklist from the docs/source/templates folder into your comment.

[noamblitz]

This seems to be the best solution to unblock regressions on main so we can release.

[sonarcloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
95.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[stephanie0x00]

Checklist for QA:

• I have checked out this branch, and successfully ran a fresh make reset.
• I confirmed that there are no unintended functional regressions in this branch:
  • I have managed to pass the onboarding flow
  • Objects and Findings are created properly
  • Tasks are created and completed properly
• I confirmed that the PR's advertised feature or hotfix works as intended.
• I checked the logs for errors and/or warnings and made issues where necessary

What works:

Looks good. There are no dangling objects. All the findings are now resolved into a severity instead of Pending. Scanned multiple hosts and enabled a lot of boefjes to verify. Report generation also works.

What doesn't work:

N/a

Bug or feature?:

n/a

[underdarknl]

Consensus is not to merge this, but revert the earlier fix. A more in depth solution should rely on xtdb2's features