feat(YouTube - Custom filter): Custom filtering of the protocol buffer

[LisoUseInAIKyrios]

This change adds the ability to filter the proto buffer using custom filters.

Syntax

• Paths can indicate an optional 'starts with' using the character: ^
  So a custom path of ^foo will hide foobar.eml|123|whatever.xyz but will not hide whatever.xyz|123|foobar_video.eml. For performance and filtering accuracy, ^ should always be used whenever possible.
• Buffer strings are optional and specified after the path using the character: $
  So a custom filter of whatever.eml will hide all UI components with a path that contains whatever.eml. But the custom filter whatever.eml$dumbo will only hide components with a path containing whatever.eml and the buffer also contains dumbo.
• Buffer strings can include spaces and any ascii symbols (including ^ and $)

Backwards compatibility with existing custom filters

All existing custom filters will continue to work, as ^ and $ are optional characters and not normally found in litho paths.

Examples

A few custom filters that are now possible:

Hide all home feed videos that contain "Mr Beast" in the channel name or video title:
^home_video_with_content.eml$Mr Beast

Hide all search result videos that contain "Mr Beast" in the title or channel name :
^search_video_with_context.eml$Mr Beast

Hide all search result videos from a specific channel (Notice there is no space after 'Mr'. This is the channel name):
^search_video_with_context.eml$- MrBeast -

Hide Shorts that contain "Mr Beast" in the title or channel name:
^shorts_video_cell$Mr Beast

Limitations

• Currently only ASCII is supported (it is possible to support unicode if there's enough interest).
• Buffer search terms are case sensitive. But you can add the same path and buffer string multiple times with different casing (ie: add both ^home_video_with_content.eml$Mr Beast and ^home_video_with_content.eml$MR BEAST). In the future it's possible to add case insensitive filtering without much performance penalty.

Integration changes

[MarcaDian]

@LisoUseInAIKyrios Hello, after the last update (on 19.16.39, v4.9.0), users write that the related_video filter does not work. Maybe you have heard about this problem and know the solution? I have this filter working on 19.16.39, v4.9.0 patches.
Maybe some a/b test or changed the name of this object.

[LisoUseInAIKyrios]

Are you referring to keyword filtering? It is probably some new layout components, and the filter needs to add additional litho component to search.

If someone can identify what the litho components are, they can be added. Turning on proto buffering helps identify what components belong to which video is on screen (search for the title of the video in the logs).