[IPPInAppFeedback] UI: Payments banner placement

[iamgabrielma]

Part of #8530

Description

This PR adds the in-app feedback banner in the Payments view, as well as the buttons to launch a survey and dismiss the banner.

At the moment the survey is only dismissible when tapping on "dismiss" (not upon survey completion), and will show up again each time we navigate to the Payments view.

TODO:

• Design has changed. Needs to be re-implemented.
• Dismissal and show me later/don't show again UI will be added on a different PR. Most probably using FeatureAnnouncementCardView

Changes

• We reuse the existing Notice component to create a feedback notice banner in the Payments View.
• Extended Notice to accept a new noticeTappedHandler handler noticeTappedHandler, so we can use 2 different behaviours: When the notice is tapped (show survey), and when the action button is tapped (dismiss notice).
• Added a new IPPFeedback case to SurveyViewController which will launch and manage the Survey launched via the tapping the notice
• Added a temporary testing survey link ( https://automattic.survey.fm/woo-app-ipp-in-app-feedback-testing ), this will dynamically change in future PRs based on certain conditions.

Testing instructions

1. Go to Menu > Payments > See the notice on the bottom of the screen
2. Tap the notice, a WebView showing a survey form will shop up. Scroll down and tap "Finish Survey", a "Feedback Sent" view will be shown and you'll be redirected to the Payments page.
3. Navigate to a different View, then navigate to Menu > Payments again.
4. Tap on "X" and see the banner disappear.

Screenshots

Feedback Banner	Give Feedback	Feedback Sent

[wpmobilebot]

You can test the changes from this Pull Request by:

• Clicking here or scanning the QR code below to access App Center
• Then installing the build number pr8532-6d73fe6 on your iPhone

If you need access to App Center, please ask a maintainer to add you.

[toupper]

Thanks for opening this PR @iamgabrielma. I added a couple of comments, and since testing might change depending on how the comments are addressed, I will wait for that before testing.
Apart from that, it might be more convenient to name the branch after the issue we have, to make it easier to link it (issue/8530-banner-placement). It can even be easier to split that big issue into smaller ones, but that's more your opinion.

[toupper]

Now that we have two inApp feedbacks, the naming looks a bit confusing to me. To make it clearer I would simply name it
generalFeedback and
IPPFeedback
We can omit the inApp prefix, we know that the feedback is triggered from the app.

[iamgabrielma]

Definitely, changed these at 34b894e and 7a13d16

[iamgabrielma]

Thanks for the review @toupper !

Due to design changes on this feature I've redone the banner to use a Notice instead, I updated the PR description, testing instructions, and screenshots with the new information. Here's also the design proposal, and how it looks right now when building the PR:

Design proposal	Current design

If this seems a good approach, I'll polish the UI further, as I may need to create a new Notice component that looks closer to what we need. I found other components in the codebase that may be helpful, like PermanentNotice, but while that one resolves some of the problems of using Notice, it also brings new ones. Happy to get any pointer if there's a better ones to use, or a better way to handle these.

it might be more convenient to name the branch after the issue we have, to make it easier to link it (issue/8530-banner-placement). It can even be easier to split that big issue into smaller ones, but that's more your opinion.

Yes, that was a mistake on my end when pushing the branch 😅 , the rest of issues are labeled and tracked in a better way.

[peril-woocommerce]

	Warnings
⚠️	This PR is assigned to a milestone which is closing in less than 2 days Please, make sure to get it merged by then or assign it to a later expiring milestone

Generated by 🚫 dangerJS

[iamgabrielma]

Closing this issue due to modifications to scope ( pdfdoF-20T-p2 ), as we won't be showing this banner anymore in the Payments view.