add default browser selection overflow menu item

[LukasPaczos]

Task/Issue URL: https://app.asana.com/0/72649045549333/1208944504536342/f

Description

Adds an overflow menu item that advertises setting DuckDuckGo as the default browser.

The introduced item is not yet used anywhere and click listeners/handlers will be added in following PRs.

Steps to test this PR

As an example, apply below diff and the item will show up whenever you open the overflow menu.

diff --git a/app/src/main/java/com/duckduckgo/app/browser/viewstate/BrowserViewState.kt b/app/src/main/java/com/duckduckgo/app/browser/viewstate/BrowserViewState.kt
index bfb487f1e..5db2efe5b 100644
--- a/app/src/main/java/com/duckduckgo/app/browser/viewstate/BrowserViewState.kt
+++ b/app/src/main/java/com/duckduckgo/app/browser/viewstate/BrowserViewState.kt
@@ -34,7 +34,7 @@ data class BrowserViewState(
     val showTabsButton: Boolean = true,
     val fireButton: HighlightableButton = HighlightableButton.Visible(),
     val showMenuButton: HighlightableButton = HighlightableButton.Visible(),
-    val showSelectDefaultBrowserMenuItem: Boolean = false,
+    val showSelectDefaultBrowserMenuItem: Boolean = true,
     val canSharePage: Boolean = false,
     val canSaveSite: Boolean = false,
     val bookmark: SavedSite.Bookmark? = null,

UI changes

Light	Dark

[malmstein]

You don’t need to change the translations, let the service do it for you. Get rid of all the strings changes, and only create new values under donottranslate.xml. Once we are done, we’ll order translations and let the process take its course.

[LukasPaczos]

You don’t need to change the translations, let the service do it for you.

I don't want to change translations, I want to reuse the one we already have in the codebase but I'm adjusting the constant's name to better reflect what it does. Is that a problem? Why would we need to run this through the service again if all the information is already there?

If I removed all the strings and added a new one that's not translated, I'd be regressing the functionality that already relies on these translations in other places.

[LukasPaczos]

Thanks @malmstein for explaining the string management process!

I reverted a2ec247 for now to avoid conflicts and I'll re-apply it in a separate translation PR.

This is ready for another round.

[malmstein]

Looks good, thanks @LukasPaczos !