chore(Cross): [IOAPPX-296] Remove native-base from dependencies

[CrisTofani]

Caution

This PR depends on #5506

Short description

This PR removes native-base and its related packages from dependencies.

List of changes proposed in this pull request

• Remove native-base and relative theme
• Remove Header and StyleProvider components
• Remove Content and Form components
• Replace legacy Toast (from native-base) with the new IOToast from io-app-design-system
• Replace legacy FooterWithButtons (based on native-base buttons) with the new FooterWithButtons from io-app-design-system
• Temporarily replace legacy ListItemComponent with Pressable native component, waiting for the complete overhaul with the new io-app-design-system components
• Replace NB's TextInput with the native one
• Remove react-native-iphone-x-helper and react-native-keyboard-aware-scroll-view unused dependencies

Warning

Known issue
Screens that use the BaseScreenComponent could be rendered with a huge amount of space on top when used in combination with SafeAreaView

For other issues, please refer to the discussion below

Credits

This PR is the result of:

• Some early group sessions with the entire IO Mobile Dev team
• Individual contributions by @CrisTofani and @dmnplb

How to test

Launch the app in the local environment and accurately test the most used flows by the citizens, especially:

• Onboarding and authentication flow
• Payment flow
• ID Pay entire flow
• Message detail with different use cases (SEND, remote content, legacy Covid cerification, etc…)

[pagopa-github-bot]

Affected stories

• ⚙️ IOAPPX-296: Rimozione native-base da io-app

Generated by 🚫 dangerJS against cb2bc47

[LazyAfternoons]

LGTM, tested different flows with a focus on FCI, including accessibility.

EDIT : I added a ticket on our cross board if that makes sense to you.

[CrisTofani]

We should check the Payments and Messages related flows to be safe. If nothing is broken, we should merge. What do you think?

It seems that the testID on TextInputValidation and TextInputPassword is not well propagated... what do you think?

@shadowsheep1 Addressed in the last 2 commits now it should be fine

[Hantex9]

LGTM!

Tested on the current payment flow and the to-be payment section and it works without any problem