feat(Bonus Pagamenti Digitali): [#177306957] Add ko service error screen

[debiff]

Short description

This PR show the ko service error screen if there is at least one KO in the searchRequestMetadata field of the privative card research response.

List of changes proposed in this pull request

• Add PrivativeKoServiceError screen
• Add SearchPrivativeCardScreen tests

[pagopa-github-bot]

Affected stories

• 🌟 #177306957: Come CIT se provo a ricercare la mia carta privativa ed almeno uno dei centri applicativi mi restituisce KO, devo visualizzare una schermata che mi informi del disservizio

Generated by 🚫 dangerJS against 7dedf31

[codecov]

Codecov Report

Merging #2904 (7dedf31) into master (3fc099b) will increase coverage by 0.38%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##           master    #2904      +/-   ##
==========================================
+ Coverage   57.99%   58.37%   +0.38%     
==========================================
  Files         882      883       +1     
  Lines       24221    24245      +24     
  Branches     4466     4467       +1     
==========================================
+ Hits        14047    14154     +107     
+ Misses      10084     9999      -85     
- Partials       90       92       +2     

Impacted Files	Coverage Δ
...g/privative/screens/add/AddPrivativeCardScreen.tsx	81.57% <ø> (+18.42%)	⬆️
...g/privative/screens/search/LoadPrivativeSearch.tsx	73.91% <ø> (+23.91%)	⬆️
...rivative/screens/search/ko/PrivativeKoNotFound.tsx	85.18% <ø> (+11.11%)	⬆️
...privative/screens/search/ko/PrivativeKoTimeout.tsx	80.55% <ø> (+19.44%)	⬆️
...tive/screens/search/ko/PrivativeKoServiceError.tsx	88.46% <88.46%> (ø)
...ative/screens/search/SearchPrivativeCardScreen.tsx	100.00% <100.00%> (+55.10%)	⬆️
...oarding/privative/store/reducers/addedPrivative.ts	71.42% <0.00%> (+9.52%)	⬆️
...arding/privative/store/reducers/addingPrivative.ts	70.00% <0.00%> (+10.00%)	⬆️
... and 8 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3fc099b...7dedf31. Read the comment docs.

[Undermaken]

Is it ok to give no UI feedback if privativeSelected is undefined?
(I could have a low context on this story)

[debiff]

This screen is managed by SearchPrivativeCardScreen.

The case in which you arrive in this screen with privativeSelected === undefined is not expected, so this is an extra layer of safety.

I removed this functions in the component because they're already called by SearchPrivativeCardScreen with the same condition and the SearchPrivativeCardScreen is the only screen that use LoadPrivativeSearch.

io-app/ts/features/wallet/onboarding/privative/screens/search/SearchPrivativeCardScreen.tsx

Lines 74 to 78 in 326c075

	if (privativeSelected === undefined) {
	showToast(I18n.t("global.genericError"), "danger");
	void mixpanelTrack("PRIVATIVE_NO_QUERY_PARAMS_ERROR");
	props.cancel();
	} else {

Do you think there is a better way to manage it?