Fix add related, fix manual ooi task list, remove redundant octopoes call

[noamblitz]

Changes

Two fixes:

• Add related now actually adds a related object instead of same ooi type
• Manually added scans show up correctly in list
• Fixes some view inheritance, increasing ooi detail speed by removing unneeded octopoes request

Demo

QA notes

Add related: go to ooi detail and click "Add" under the related objects. Show now work again.

After adding a raw file, in the ooi detail, the observation should now show: Scan was added manually.

Whole ooi detail should be QA'ed because the view inheritance has changed so there is a chance of regressions.

---

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.

[dekkers]

Not really blocking, but maybe "The raw file was uploaded manually" or "This scan was done manually" is better than "This scan was manually created"? In the case OOIs are just added manually they don't have to be the result of a scan, so I think saying that there was a manual upload instead of scan is more accurate.

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

Tested that the dropdown shows up when clicking the 'Add' button on a 'Related Objects' page. This works.
Manually added a DnsRecords scan, by downloading old DNSRecords, changing the data and re-uploading this. The data shows up in the tree and the objects can be clicked. The testdomain that was used has the same clearance levels as the domaindiscount24.net domains that result from the onboarding scans for mispo.es.
I also added a manual HostnameHTTPURL and that receives the same clearance level as a different HostnameHTTPURL for the same domain.
The DNS Records task can be rescheduled and runs accordingly.
Tested a migration scenario from main, by performing the step above. This seems to work.

Links from the normalizers (from newly added objects) also are clickable from the normalizer Tasks tab.
The added testdomain also shows up in the object tree for mispo.es.

What doesn't work:

n/a

Bug or feature?:

n/a

[ammar92]

Looks good to me. Very minimal remarks, consider it approved