Fix compile warnings

[ZardenSawtooth]

Fixed several compile warnings

♻️ Current situation & Problem

Fixed the following compile warnings to maintain a cleaner compile window.

src/components/AdvancedQuestionOptions/AdvancedQuestionOptions.tsx
  Line 266:33:  img elements must have an alt prop, either with meaningful text, or an empty string for decorative images  jsx-a11y/alt-text

src/components/Languages/Translation/TranslateSettings.tsx
  Line 38:44:  Array.prototype.map() expects a return value from arrow function  array-callback-return

src/components/Metadata/MetadataEditor.tsx
  Line 34:11:  'getUseContextSystem' is assigned a value but never used  @typescript-eslint/no-unused-vars

src/components/Navbar/Navbar.tsx
  Line 119:90:  The href attribute is required for an anchor to be keyboard accessible. Provide a valid, navigable address as the href value. If you cannot provide an href, but still need the element to resemble a link, use a button and change it with appropriate styles. Learn more: https://github.com/evcohen/eslint-plugin-jsx-a11y/blob/master/docs/rules/anchor-is-valid.md  jsx-a11y/anchor-is-valid

src/components/Question/Question.tsx
  Line 18:31:  'isItemControlReceiverComponent' is defined but never used   @typescript-eslint/no-unused-vars
  Line 39:5:   'canTypeHaveSublabel' is defined but never used              @typescript-eslint/no-unused-vars
  Line 57:33:  'setIsMarkdownActivated' is assigned a value but never used  @typescript-eslint/no-unused-vars
  Line 78:11:  'getSublabelText' is assigned a value but never used
@typescript-eslint/no-unused-vars

src/components/Question/QuestionType/Choice.tsx
  Line 24:50:  'isItemControlDropDown' is defined but never used  @typescript-eslint/no-unused-vars

✅ Testing

Ensured that the compile warnings are gone.

Code of Conduct & Contributing Guidelines

By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

• I agree to follow the Code of Conduct and Contributing Guidelines.

[vishnuravi]

Thank you for your PR @ZardenSawtooth! I've added a few comments. Feel free to follow up with any questions you have.

cc: @PSchmiedmayer

[vishnuravi]

This change appears to have caused a side effect whereby the title is now styled as an underlined hyperlink as opposed to white text, and the color clashes with the navbar making it hard to read. Is there another method of resolving this warning that would preserve the original styling?

[vishnuravi]

There appears to be some code referencing this helper function that is currently commented out. If this function is to be removed, I would also recommend removing the commented out code that is referencing it.

[vishnuravi]

If we are removing the function that allows us to set this state variable, what is the purpose of keeping the state variable? Can we remove it all together and refactor the code referencing it?