Make the "name" field for plugins mandatory

[Donnype]

Changes

A follow up on #3444 where we make the name field required at the model level as well.

Issue link

This should fix the issue with the database models where the name is not nullable, and make sure we can use the name field for human readables now that we will start generating UUIDs for plugins ids. This PR also adds some names that were still missing.

Demo

QA notes

This does not add features, please verify that the boefjes and normalizers run properly still!

---

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.

---

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.

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

All the enabled boefjes and normalizers run as expected.

What doesn't work:

n/a

Bug or feature?:

n/a