Add guide for auto connect and lockdown mode

[Pururun]

This is a continuation of: #5592

---

This change is 

[linear]

DROID-548 Add guide for auto-connect and lockdown mode

[sabercodic]

Reviewed 18 of 18 files at r1, 5 of 5 files at r2, 1 of 1 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved

[Pururun]

This is on hold waiting for design review.

[Pururun]

This is now on hold waiting for input from @Rawa

[Pururun]

This has been approved by design and @Rawa so it is now open for review again.

[Rawa]

Reviewed 1 of 2 files at r4, 1 of 2 files at r5, 4 of 4 files at r6, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @Pururun)

---

android/app/src/main/kotlin/net/mullvad/mullvadvpn/compose/component/AutoConnectCarousel.kt line 72 at r6 (raw file):

@OptIn(ExperimentalFoundationApi::class)
@Composable
fun AutoConnectCarousel() {

This function is a bit long, possibly worth considering breaking it apart to:

• PageContent (Insides of the horizontal pager)
• PageIndicator (Last Row in this function

---

android/app/src/main/kotlin/net/mullvad/mullvadvpn/compose/screen/VpnSettingsScreen.kt line 297 at r6 (raw file):

        snackbarHostState = snackbarHostState
    ) { modifier, lazyListState ->
        val context = LocalContext.current

I think we should avoid using LocalContext.current as much as possible, also if VPN settings are available is something that should be described into the view state. Maybe creating a UseCase that injects the applicationContext to find this information out is a better alternative?

[Pururun]

Reviewable status: 20 of 29 files reviewed, 2 unresolved discussions (waiting on @Rawa and @sabercodic)

---

android/app/src/main/kotlin/net/mullvad/mullvadvpn/compose/screen/VpnSettingsScreen.kt line 297 at r6 (raw file):

Previously, Rawa (David Göransson) wrote…

I think we should avoid using LocalContext.current as much as possible, also if VPN settings are available is something that should be described into the view state. Maybe creating a UseCase that injects the applicationContext to find this information out is a better alternative?

Added UseCase

---

android/app/src/main/kotlin/net/mullvad/mullvadvpn/compose/component/AutoConnectCarousel.kt line 72 at r6 (raw file):

Previously, Rawa (David Göransson) wrote…

This function is a bit long, possibly worth considering breaking it apart to:

• PageContent (Insides of the horizontal pager)
• PageIndicator (Last Row in this function

I made the screen more to how we made our other screens.

[Rawa]

Reviewed 11 of 11 files at r7, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Pururun)

---

android/app/src/main/kotlin/net/mullvad/mullvadvpn/compose/screen/VpnSettingsScreen.kt line 297 at r6 (raw file):

Previously, Pururun (Jonatan Rhodin) wrote…

Added UseCase

Nice! 👏

---

android/app/src/main/kotlin/net/mullvad/mullvadvpn/compose/component/AutoConnectCarousel.kt line 72 at r6 (raw file):

Previously, Pururun (Jonatan Rhodin) wrote…

I made the screen more to how we made our other screens.

Good job! 🥇

[Rawa]

Reviewable status: complete! all files reviewed, all discussions resolved

[Rawa]

Reviewed 1 of 2 files at r8, 3 of 3 files at r9, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved

[albin-mullvad]

Reviewed 1 of 3 files at r9.
Reviewable status: complete! all files reviewed, all discussions resolved