Update scheduler folder structure

[jpbruinsslot]

Changes

Refactoring of folders, cherry-picked from #3839 to make that PR a bit more easier to review in the future.

• Move alembic/ migrations into storage/
• Moved config/ into context/ resulted in build-docs problems, left it in config/
• Renamed connectors/ to clients/
• Renamed listeners/ to amqp/
• Renamed services/ to http/
• Moved queues/ into schedulers/
• Moved rankers/ into schedulers/

From:

./
├── alembic/
├── config/
├── connectors/
│   ├── listeners/
│   └── services/
├── context/
├── models/
├── queues/
├── rankers/
├── schedulers/
├── server/
├── storage/
└── utils/

To:

./
├── clients/
│   ├── amqp/
│   └── http/
├── context/
├── models/
├── schedulers/
│   ├── queue/
│   ├── rankers/
│   └── schedulers/
├── server/
├── storage/
│   ├── migrations/
│   └── stores/
└── utils/

QA notes

Please add some information for QA on how to test the newly created code.

---

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.
• 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.

[ammar92]

Looks good to me. Only the schedulers.schedulers package is a bit confusing, but not blocking for now

[jpbruinsslot]

Looks good to me. Only the schedulers.schedulers package is a bit confusing, but not blocking for now

Thanks for checking. Yeah I agree, I'm open to suggestions.

[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:

Onboarding works, added an extra hostname and enabled some additional boefjes. Scheduled a report which runs on the every minute interval as expected. Subreports can be opened and the main report as well. Aggregate report can be generated. Stopped the scheduler to see what would break. Reports can still be opened and on the Tasks page the expected Error messages are shown.

What doesn't work:

n/a

Bug or feature?:

n/a

[sonarcloud]

Quality Gate failed

Failed conditions
35.9% Coverage on New Code (required ≥ 80%)
5.0% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud