A4A-Partner Directory: Add to step 3 a publish CTA button

[cleacos]

Resolves: https://github.com/Automattic/automattic-for-agencies-dev/issues/699
Resolves: https://github.com/Automattic/automattic-for-agencies-dev/issues/701

Proposed Changes

This PR adds the step-3 Publish button:

• Extract and apply some validation code (URLs) as tools
• Allow to save the agency details at any time, without the required fields.
• Shows step 1 when it's the first time the agency is applying.
• Add the Publish button in step 3. Once the agency completes the steps 1 and 2, they can publish the application.

Why are these changes being made?

Testing Instructions

• Apply for a few directories
• Get approved from at least one of them. Use the MC tool for approve it: /agencies/partner-directory.php?mca4a_agency_id={your_agency_id}
• You can restore your application using the endpoint directly: PUT https://public-api.wordpress.com/wpcom/v2/agency/{your_agency_id}/profile/application

Dummy data:

{
    "products": [
        "woocommerce",
        "jetpack"
    ],
	  "services": ["content_strategy_development"],
    "directories": [
        {
					"directory": "wordpress",
					"urls": [
						"https:\/\/example11.com",
						"https:\/\/example2.com",
						"https:\/\/example3.com",
						"https:\/\/example4.com",
						"https:\/\/example5.com"
					],
					"note": "My WordPress.com application",
					"is_published": false,
					"status": "pending"
        },
        {
					"directory": "jetpack",
					"urls": [
						"https:\/\/example1.com",
						"https:\/\/example2.com",
						"https:\/\/example3.com",
						"https:\/\/example4.com",
						"https:\/\/example55.com"
					],
					"note": "My Jetpack.com application",
					"is_published": false,
					"status": "pending"
				}
    ],
    "status": "in-progress",
    "feedback_url": "https://example3.com",
		"is_published": false
}

• Edit agency expertise
• Edit agency profile
• Click on the Publish button:
• You will see:

and the summary Congratulation page:

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-112371

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-112371&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-112371&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~308 bytes added 📈 [gzipped])

name                                parsed_size           gzip_size
a8c-for-agencies-partner-directory       +951 B  (+0.2%)     +308 B  (+0.2%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/a4a/partner-directory-add-step-3-publish-cta on your sandbox.

[vitozev]

It works as expected and the code changes makes sense to me 👍

[vitozev]

Minor: In this case I think you will be able to enter $ as a value for instance and validation will pass.

[cleacos]

Yep. The validations will be updated in this PR: #92123

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/15476154

Some locales (Hebrew, Japanese) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday.

Thank you @cleacos for including a screenshot in the description! This is really helpful for our translators.

[a8ci18n]

Translation for this Pull Request has now been finished.