LF-4056b Fix for language selector dropdown

[kathyavini]

Description

When I migrated to the new useLanguageOptions hook in this PR:

• LF-4400 Add new languages to i18n framework #3409

I completely missed that components/Profile/Account expected to see the options in a map format, not in the React Select Options array format expected by components/InviteUser and components/Profile/EditUser.

The hook only returns the array shape, so the code that sets the languagePreferenceOptionRef no longer created the correct React Select option shape, and as a result the language became unselected when you saved a new language_preference.

I also considered updating the hook to return either map or array depending on the calling component (i.e. to accept a parameter like returnType = 'map' | 'array', but I thought it seemed cleaner to update the account code to work with the options array as the other two components do.

Also in this PR:

• There was a 100ms nulling of the selected language upon change which flashes the unselected state (you can still see it on app) -- maybe this had a purpose at some point (giving translations time to load or such maybe, according to comment?) but I certainly didn't see such a purpose now so I have deleted it. Therefore no more flash.
• I forgot to delete the t() function from the useLanguageOptions hook when I updated the language dropdown options in LF-4056 Language selector needs to provide list of language in their native form #3416 (at which point they are no longer sent through i18n)

Jira link: https://lite-farm.atlassian.net/browse/LF-4056?focusedCommentId=17638 (linking to comment describing the bug)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Passes test case
• UI components visually reviewed on desktop view
• UI components visually reviewed on mobile view
• Other (please explain)

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The precommit and linting ran successfully
• I have added or updated language tags for text that's part of the UI
• I have added "MISSING" for all new language tags to languages I don't speak
• I have added the GNU General Public License to all new files