feat: totally hide strict filters

[ayoayco]

As discussed on the #ux channel, there is more demand to totally hide filtered posts when the FilterAction is 'hide'

This PR will

1. remove displaying "Removed by filter: phrase' from the StatusCard component
2. implement context for the paginator
3. implement filtering logic in the reorderedTimeline function
4. add tests of filtering scenarios for reorderedTimeline function

Changes 2-4 are needed for when the feature virtualScroller is true, because it adds an empty DynamicScroller

Also, some initial styling fix for warning filters if it is a DM:

before	after

Handle contexts:

• Home and lists
• Notifications
• Public timelines
• Conversations
• Profiles

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[netlify]

✅ Deploy Preview for elk-docs canceled.

Name	Link
🔨 Latest commit	eac0590
🔍 Latest deploy log	https://app.netlify.com/sites/elk-docs/deploys/63cedfdcf4b5f10008b2eea1

[netlify]

✅ Deploy Preview for elk-zone ready!

Name	Link
🔨 Latest commit	eac0590
🔍 Latest deploy log	https://app.netlify.com/sites/elk-zone/deploys/63cedfdc6d7f440008c8e108
😎 Deploy Preview	https://deploy-preview-948--elk-zone.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[patak-dev]

I like that once preprocessed, we avoid dealing with these posts. One issue here is that if the user changes a strict filter, then a reload is needed to show these posts but I think the tradeoff is ok here.

[ayoayco]

This branch already works (so if there's more demand it can be merged), but I plan to refactor it.

You can compose the strict filter and the reorderTimeline and pass it as a single param to avoid the need of passing the context all the way down

I'm looking to implement this suggestion in the previous comment by @patak-dev

[patak-dev]

Lets do the refactoring first, no rush