[Issue] Fixed frontend resize for product configurations images

[m2-assistant]

This issue is automatically created based on existing pull request: #31274: Fixed frontend resize for product configurations images

---

Description (*)

When creating new configurations from the configurable product page wizard, the images of the configurations are not resized on the frontend via javascript before uploading. This is caused by a misconfiguration of the jQuery File Upload widget.
I copied the options from the media-uploader.js file (app/code/Magento/Backend/view/adminhtml/web/js/media-uploader.js).

Manual testing scenarios (*)

1. Go in the New product page
2. Fill in the required fields
3. Click on Create configurations button
4. In the wizard select an attribute and one or more attribute values
5. In the third step, in the Images section, select Apply single set of images to all SKUs
6. Select an image to upload (must have width greater than 1920px or height greater than 1200px)
7. The preview dimensions will have a maximum width of 1920px and a maximum height of 1200px. (without this fix the preview has the same dimensions as the original image).

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.

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-39937 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.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.