feat (YouTube/ReVanced Settings): Improve ReVanced Settings UI

[ILoveOpenSourceApplications]

Feature description

Currently, ReVanced settings include sub setting descriptions and line separations, which deviate from the default YouTube settings page. This issue proposes removing these elements to align ReVanced settings with the aesthetic and consistency of the YouTube UI.

Now:

After Implementing Changes:

Motivation

Aligning ReVanced settings with the default YouTube settings page enhances the user experience by providing a familiar and consistent interface. Removing sub setting descriptions and line separations not only streamlines the visual appearance but also promotes clarity and ease of navigation. Users accustomed to YouTube's UI will find the transition to ReVanced smoother, resulting in a more cohesive and aesthetically pleasing experience overall.

Acknowledgements

• This issue is not a duplicate of an existing feature request.
• I have chosen an appropriate title.
• All requested information has been provided properly.

[MarcaDian]

I was tired of waiting for these changes, so I made it myself. but I'm still waiting for it to happen.
I’m also looking forward to a rethink of the menu items, especially the Layout.
#2629 (comment)

[oSumAtrIX]

#2629

[ILoveOpenSourceApplications]

@oSumAtrIX ,I don't think #2629 can be called a duplicate of my issue, as what @LisoUseInAIKyrios is requesting and what I'm requesting is entirely different. But still, if both can be clubbed together and implemented, I'm fine with that as well.

[oSumAtrIX]

I don't see the difference

[ILoveOpenSourceApplications]

I don't see the difference

That's striving more towards better navigation and user friendly settings page while this is for UI improvements and consistency.

[oSumAtrIX]

I guess you could add a comment about that in the other issue, because they would be both involved in the same PR/commit

[ILoveOpenSourceApplications]

I already did leave a comment regarding an issue #388, which is more in-line with this issue as both are visual changes compared to the navigation and ease of use changes of #2629, but @LisoUseInAIKyrios said it's slightly different than what his issues is and hence I opened this new issue.