Basic NetP remote messaging

[samsymons]

Task/Issue URL: https://app.asana.com/0/0/1205553443275690/f
Tech Design URL:
CC:

Description:

This PR adds basic remote messaging support for NetP.

This feature pings a new URL for messages to display, where each message can optionally include a number of days that NetP has to be active for it to be displayed, and an optional URL to open when the user clicks the action button.

This feature will be used by us to deliver surveys to users, and to tell them when the beta is ending.

This feature was built for NetP, so each card just uses a NetP icon.

Steps to test this PR:

First, activate NetP:

1. Reset NetP state completely
2. Turn on the NetP waitlist active and waitlist beta feature flags in the debug menu
3. Join the waitlist
4. After you join the waitlist, use the debug menu to bypass the invite code flow and let you into the beta by entering your own invite code (let me know if that doesn't work, we haven't really used that feature since the ship review)

Now, test the remote messages:

1. Background and foreground the app a couple times, to give the app a chance to trigger the remote message fetch and refresh the new tab page
2. Open the new tab page
3. Check that you have a single new message in the new tab page titled "Initial Card"
4. Go to the Debug menu's Network Protection setting and pick "Set Activation Date to 10 Days Ago" from the NetP Activation Override menu
5. Go back to the new tab page and check that two new cards have appeared
6. Check that you can click the survey link on the last card and it opens a new tab, then when you go back to the new tab page it's gone
7. Test dismissing the other two messages via the X or Dismiss buttons
8. Open a new window/tab and verify that the messages are gone

How to test pixels:

1. Turn on Logging in the Debug menu via Debug -> Logging -> Pixel
2. Set your activation date to 10 days via Debug -> Network Protection -> Override NetP Activation Date -> Set Activation Date to 10 Days Ago
3. Reset cards via Debug -> Network Protection -> Reset Remote Messages
4. Reset daily pixel state via Debug -> Reset Data -> Reset Daily Pixels
5. Background and foreground the app a couple times to have it trigger remote message fetch and update the new tab page
6. Once cards have appeared, you should see three pixel log entries like m.mac.netp.remote.message.displayed.456.d
7. Click the "Take Survey" button on the third card and you should see m.mac.netp.remote.message.opened.789
8. Click the X button on the first and the Dismiss button on the second card, and you should see logs like m.mac.netp.remote.message.dismissed.123 for each of them

---

Internal references:

Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation

[github-actions]

	Warnings
⚠️	PR has more than 500 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS against 793c4f3

[diegoreymendez]

Hey @samsymons - I can't make "Initial Card" come up for me. I'm following the instructions. Any thoughts of things I could try?

[diegoreymendez]

Works as described in the testing steps.

A few suggestions:

• It would be nice if resetting NetP also reset both the activation date, and the survey card.
• I haven't tested pixels since there aren't specific testing instructions. Do you think you could sum up testing instructions for those so I can double check?
• Could you expand a bit on the "rate limited operation" concept? I'm having a bit of trouble understanding the rate limiting bit in the context of this PR. Just an explanation of why thats needed / how it's necessary.

[samsymons]

@diegoreymendez

1. I've updated the reset option for NetP to remove activation state and messages
2. I've added a new debug menu option to reset Daily Pixel state
3. I've added a option to reset remote messages specifically, in case you want to reset those without resetting all of NetP
4. I added a little doc comment to the rate limited operation class - let me know if it's clear, please don't hesitate to push back if it's not, or if you think the class name/design could use improvement
5. I added a section to the description titled How to test pixels which should give you everything you need to test them, let me know if anything there doesn't work

I think that should address all the feedback 🙏

[samsymons]

Note that SwiftLint is failing on this PR because CI has updated it. I'll open a PR to fix lint warnings against develop in a separate PR.

[diegoreymendez]

Added some additional review comments. The optional ones can be safely ignored... the 1 that I think is slightly more important is the one about thread safety, but it should also be easy to address.