Add slim endpoints for entities to speed up filters

[ghost]

Should resolve issue #452

In my library with 123 performers and 1MB-ish performer images it speeds up AllPerformersForFilters from 0.4s to 0.04s. For 549 studios it speeds up from 0.08s to 0.02s.

I considered changing the dropdowns to fetch on demand, but considering that scenes can have arbitrary amount of performers attached, it would likely make page load significantly slower in many instances.

[bnkai]

I can confirm 7x-8x speedup also for the performers and studios part
(536 Performers 627 Studios in my db)

[WithoutPants]

Testing against a database with 1,968 performers, I'm not seeing any difference before and after this change. I'm seeing between 7.5 and 12 seconds for allPerformersSlim to come back.

[ghost]

@WithoutPants Try now. I've added a migration that moves the image column to the end of the table. Apparently selecting columns past blobs incurs a large penalty in sqlite. On my instance it reduces the allPerformers query further down to 0.01s, though it seems my dataset isn't large enough to really stress the database at this point. I'm guessing at a certain size it spills to disk, causing the crazy query times.

[bnkai]

I was getting consistent speedup in the edit scene tab as stated above also. @WithoutPants is your db maybe in a spinning disk? ( my tests were in sata ssd and nvme ssd)

[bnkai]

With latest commit :
Database located on a nvme ssd
Edit Scene Tab
Firefox as browser

Time for AllPerformers
500+ performers
before 800ms after 15-20 ms
1k+ performers
before 1150ms after 25-30 ms

[WithoutPants]

I'm getting consistent times of around 50ms for allPerformersSlim now. Looks good.

[WithoutPants]

I think we should take the opportunity to remove the redundant index.