Fix keyboard navigation for various settings

[yugalkaushik]

Fixes #3448

Changes:

• Improved keyboard navigation across all preference settings.
• Ensured that disabled radio buttons remain focusable via keyboard for accessibility .
• Fixed inconsistent focus ring color and thickness between theme selection and other settings.
• Increased the overall size of the Preferences component slightly to prevent partial button visibility and reduce unnecessary scrolling.

general.setting.mp4

I have verified that this pull request:

• has no linting errors (npm run lint)
• has no test errors (npm run test)
• is from a uniquely-named feature branch and is up to date with the develop branch.
• is descriptively named and links to an issue number, i.e. Fixes #123

[yugalkaushik]

@Jatin24062005 Can you review this PR please.

[Jatin24062005]

@yugalkaushik I’ve reviewed your pull request and tested it on my machine. I noticed a couple of issues: the keyboard navigation currently allows focusing only on enabled buttons, but it should also allow navigation to disabled buttons like Similar to the High Contrast and Dark theme options. Additionally, the focus border appears slightly thicker than the standard one, which creates inconsistency in the UI. Please look into these issues and make the necessary adjustments.

[yugalkaushik]

1. I’ve tried many different approaches, but keyboard navigation only works for enabled buttons because the On and Off options share the same name, which is essential for proper radio button functionality but can be selected using left and right arrow keys. In contrast, the theme buttons use different name attributes, so they behave like separate buttons, allowing focus on other states.

2. Fixed inconsistent focus ring color when navigating with the keyboard.

3. The original size of the Preferences component was not practical, as only half of some buttons were visible and required scrolling. So, I slightly increased the overall size for better usability.

   Before:
   
   After:
   

[yugalkaushik]

@raclim can you please review.

[raclim]

Thanks so much for your work on this!

After testing this out, I think this is overall a positive change and would be great to have out. We could definitely add any needed adjustments here in the future!