[PAY-2037] Improve web usdc purchases validation

[raymondjacobson]

Description

• Fix desired behavior when a user taps Premium (Pay-to-unlock), but enters no values for price and then loses focus. I think there's a lot of coupling going on here between the validation types and the actual track object types. Over time, I think we need to tease those apart.
• Allows the user to correctly unset a USDC purchase option by switching back to public. We still have some bugs where special access does not override usdc_purchase correctly (formik seems to shallow merge). Will address in a separate PR
• Makes it so fields can be required in the Access&Sale section

• Fixes small bug (PAY-2055) where price on mobile starts at 0 instead of a placeholder value (making experience similar to web)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide repro instructions & any configuration.

• regular upload
• premium usdc + preview upload
• follow gated upload
• remix upload
• hidden upload

[audius-infra]

Preview this change https://demo.audius.co/rj-pay-2037

[audius-infra]

Preview this change https://demo.audius.co/rj-pay-2037

[audius-infra]

Preview this change https://demo.audius.co/rj-pay-2037

[raymondjacobson]

Merging this PR into sd-usdc-remix-stem-mobile because @sddioulde touched similar things

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@storybook/jest	0.2.3	None	+8	746 kB	yannbf
@storybook/testing-library	0.2.2	None	+1	511 kB	yannbf
@storybook/test-runner	0.13.0	network, filesystem, shell, environment	+78	13.5 MB	shilman
@storybook/addon-interactions	7.5.1	network	+14	6.69 MB	shilman
@testing-library/react-native	12.3.0	environment	+0	590 kB	mdjastrzebski
react-twitter-embed	3.0.3...4.0.4	None	+0/-7	139 kB	saurabhnemade

🚮 Removed packages:@types/react-test-renderer@16.9.0

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Invalid package.json	@jest/globals	28.1.3	Location:Package overview	@storybook/test-runner@0.13.0 via packages/harmony/package.json

Next steps

What is an invalid package.json?

Package has an invalid package.json and can cause installation problems if you try to use it.

Fix syntax errors in the invalid package.json and publish a new version with a valid package.json. Consumers can use npm overrides to force a version that does not have this problem if one exists.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore @jest/globals@28.1.3