Forms: Make file upload field block available in beta and refine its behavior

[lezama]

Fixes #

Proposed changes:

• Updates the file upload field block from experimental to beta status
• Uses the WordPress upload icon for better visual consistency
• Prevents the file dialog from opening when clicking the field in the editor
• Simplifies block registration to only handle beta blocks, removing experimental block handling
• Updates PHP registration to match JavaScript block registration
• Improves code organization by keeping the file upload field in the childBlocks array

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?

Testing instructions:

1. Enable beta blocks by adding this to your 0-sandbox.php:

   define( 'JETPACK_BLOCKS_VARIATION', 'beta' );

   Or by using the filter:

   add_filter( 'jetpack_blocks_variation', function () { return 'beta'; } );

2. Create or edit a post with the Jetpack Form block

3. Add a new field to the form

4. Verify that:

   • The File Upload field is available in the field options
   • The field uses the WordPress upload icon (instead of a custom icon)
   • The field appears correctly in the editor
   • Clicking the field in the editor does not trigger the file dialog (it should only be interactive on the frontend)
   • The field preview behaves consistently with other form fields

This PR builds upon the work done in #41582, which introduced the initial file upload field implementation. The main changes are moving the block from experimental to beta status and refining its behavior in the editor to be more consistent with WordPress patterns.

[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 update/forms-file-upload-field-refinements branch.

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

  bin/jetpack-downloader test jetpack update/forms-file-upload-field-refinements
  

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

[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 a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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.

---

🔴 Action required: We would recommend that you add a section to the PR description to specify whether this PR includes any changes to data or privacy, like so:

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

My PR adds *x* and *y*.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[github-actions]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/forms/src/blocks/contact-form/components/jetpack-field.js	0/18 (0.00%)	0.00%	1 💔

Full summary · PHP report · JS report

[enejb]

The PR tested as expected for me.

When I have the define( 'JETPACK_BLOCKS_VARIATION', 'beta' ); the block shows up for me and when I have
define( 'JETPACK_BLOCKS_VARIATION', 'experimental' ); it does not.