fix wrong top boost

[pory-gone]

Description

fix #2663
The boostPosition resolver was missing pinId and bio filters that are present in getAd causing wrong boost estimates.

Screenshots

Additional Context

When a user wanted to pin a post to the homepage, SN showed the wrong cost because it included posts that would never be visible to that user (NSFW posts, muted users, muted subs)
When a user wanted to boost a post to the top, SN showed the wrong cost because boostPosition was counting items that would never appear as boosted ads as Bio post and Pinned post.
if a Bio post had 500k boost and a normal post had 100k boost, boostPosition would incorrectly return 500k as the max boost, while getAd would correctly show the 100k normal post as the top ad.

Checklist

Are your changes backward compatible? Please answer below:
Yes

On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
8/10
I tested all filter combinations via SQL queries simulating the resolver logic: logged out users, logged in with NSFW on/off, user mute, sub mute, and viewing specific subs. Tested all filter combinations via SQL queries: bio posts, pinned posts, deleted posts, outlawed posts, stopped posts, and different subs.

For frontend changes: Tested on mobile, light and dark mode? Please answer below:
NaN

Did you introduce any new environment variables? If so, call them out explicitly here:
NaN

Did you use AI for this? If so, how much did it assist you?
AI helped me generating the SQL test queries to check all filter combinations