[Issue] Don't load datepicker module until it is actually needed

[m2-assistant]

(i) This ticket is created automatically based on a verified GitHub issue.

{panel}
If you are starting to work on this Jira ticket, please notify issue reporter and authors of related community pull requests (if any) that you are going to work on this issue:

1. Assign #28823 issue to yourself on Magento GitHub
2. Add comment "Internal Magento team is working on this issue right now."
   {panel}
   This issue is automatically created based on existing pull request: Don't load datepicker module until it is actually needed #27860: Don't load datepicker module until it is actually needed ------- ###### Description (*)

Magento 2.4-develop
This PR is a part of my effort to improve Magento 2 frontend performance.

Goal here is to eliminate unnecessary loading of datepicker UI component, which is only needed when the shop has date of birth field enabled.

Expected behavior (*)

1. Enable date of birth field for customers in admin.
2. Verify that jquery/ui-modules/datepicker.js is not loaded on pages that do not use datepicker (e.g. homepage, category, product etc.).
3. Verify that above file is loaded and datepicker works properly on pages that use it (e.g. customer registration form page).

Benefits

Performance improvement
Tested on Magento 2.4-develop with Luma and sample data.

• 205 -> 202 JS requests (-1.46%).
• 698.40kB -> 652.57kB JS transferred (-6.56%).

Additional information

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 @engcom-Delta. 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.