Fix the retrieval of plugins

[pyrco]

No description provided.

[codecov]

Codecov Report

Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (688dcb9) 73.94% compared to head (f67024e) 73.95%.

Files	Patch %	Lines
dissect/target/plugin.py	91.07%	5 Missing ⚠️
dissect/target/tools/query.py	75.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #476   +/-   ##
=======================================
  Coverage   73.94%   73.95%           
=======================================
  Files         260      260           
  Lines       21032    21017   -15     
=======================================
- Hits        15553    15543   -10     
+ Misses       5479     5474    -5     

Flag	Coverage Δ
unittests	73.95% <89.06%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Schamper]

I've been meaning to also change some of the way plugins are stored in the tree. Right now it's sub-optimal for the default and preferred method of retrieving plugins (by function name).

I was thinking of making the tree function-first, so e.g.:

{
    "services": [{<windows services plugin definition>}, {unix services plugin definition}]
}

This would optimize for the happy path of plugin retrieval.

Since you're touching a lot of the plugin system here, could this fit in this PR or make it easier to change the tree to that format in the future?

[pyrco]

I think that is a bit too different scope for this change. It also needs a bit more thinking and designing. So for another time.