CRM: Resolves 3389 - remove axios dependencies

[tbradsha]

CRM: Resolves Automattic/zero-bs-crm#3389 - remove axios dependencies

Proposed changes:

In #34238 the axios dependency was updated. However, we really don't even need this dependency, as we can just use fetch.

This PR removes the axios dependency in favor of fetch, adding a small callAutomationsAPI wrapper function. I also fixed a few React errors due to items not having a key prop and table data not being wrapped in <thead> and <tbody>.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

No functionality should have changed between trunk and the fix/crm/3389-remove_axios_dependencies branch. Likewise, automations is behind a feature flag.

1. Enable automations feature flag:

   add_filter( 'jetpack_crm_feature_flag_automations', '__return_true' );
   add_filter( 'jetpack_crm_feature_flag_api_v4', '__return_true' );
   

2. Go to the automations dashboard: /wp-admin/admin.php?page=jpcrm-automations#/automations
3. Ensure it is populated with any workflows you'd previously added, and that you can edit them. If you don't have any, there are two example workflows in CRM: Add Send_Email action + create a typical real automation scenario for a business #33424.

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the fix/crm/3389-remove_axios_dependencies branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack fix/crm/3389-remove_axios_dependencies
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin fix/crm/3389-remove_axios_dependencies
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[coder-karen]

This tests well for me .