[Issue] Add missing "VAT Number" field to customer registration page

[m2-assistant]

This issue is automatically created based on existing pull request: #31321: Add missing "VAT Number" field to customer registration page

---

Description

This commits makes "VAT Number" field visible when customer/create_account/vat_frontend_visibility is enabled.
The code was copied from nearby address/edit.phtml template.

Manual testing scenarios

1. Enable Show VAT Number on Storefront option at Stores > Configuration > Customers > Customer Configuration > Create New Account Options > Show VAT Number on Storefront
2. Navigate to frontend and add some product to the cart.
3. Proceed to Multishipping checkout and select "Create Account" option
4. Address fields are shown but "VAT Number" field is missing.

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @krishprakash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[krishprakash]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @krishprakash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @krishprakash, here is your Magento Instance: https://44d9708e09d0833566fb4827bd082187-2-4-develop.instances.magento-community.engineering
Admin access: https://44d9708e09d0833566fb4827bd082187-2-4-develop.instances.magento-community.engineering/admin_696d
Login: 622facfb
Password: 07c8fc59ba98

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-40016 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[gabrieldagama]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #31321 by @vovayatsyuk in 2.4-develop branch
Related commit(s):

• e5444ad190e86c06855006518fb9b32486ca2d0a
• 01f31854e750178280ec7b8ae92844e01e5204f9
• d01133d13f6d130d5497a891a4e0ea3195a7bcac
• 13b966a959f74a4975b24f22a6d3b169b54f9822
• ecc30d55c6639a2d18b4524835f50c79c96eef4a
• 837a48a168711d1df0085442cc754f26e48d0927
• 8b4e8b5c81a0faa6435290ce1607cf707cd1977a
• 93a0469c2fbb87dae6e0baf07cd6ae06e79e258b
• 1f9802ddb6bf67cc9d70d9e468787f1c1e1e27f2
• 6bd52c9757b2560cb8fe5ae20e007d52d4fd8390
• a24dce44ce86c4a1981de0c15235eca911c0d8f8
• c9bcf3df6bfca182283db8f033ee6d02d5ff4e2e
• 71428b52f8cf724bdae62b00052b7ab2060cc1f5

The fix will be available with the upcoming 2.4.3 release.

[magento-engcom-team]

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

Please feel free to comment or reopen according to the Issue reporting guidelines
the ticket if you are still facing this issue on the latest 2.x-develop branch. Thank you for collaboration.