feat: adding named exports for react datepicker

[skitscha]

Description

This PR aims to resolve issue 4039

Problem
An consumer of this library gets the error JSX element type 'DatePicker' does not have any construct or call signatures when importing this library when they have the moduleResolution nodenext/node16.

Changes
Add an named export of the main DatePicker picker component so that users have alternative methods to import this library other than the current default export.

To reviewers

Contribution checklist

• I have followed the contributing guidelines.
• I have added sufficient test coverage for my changes.
• I have formatted my code with Prettier and checked for linting issues with ESLint for code readability.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.12%. Comparing base (ec4ce2c) to head (645eda5).
⚠️ Report is 32 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5749   +/-   ##
=======================================
  Coverage   97.12%   97.12%           
=======================================
  Files          30       30           
  Lines        3374     3375    +1     
  Branches     1424     1408   -16     
=======================================
+ Hits         3277     3278    +1     
- Misses         95       97    +2     
+ Partials        2        0    -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.