fix(cloudfront-signer): parse date using Date constructor

[smilkuri]

Issue

#6403

Description

This PR adds changes in the parseDate function to use date constructor instead of Date.parse() to support timestamps in milliseconds.

Testing

Locally by testing it with milliseconds and date format string inputs.

✓ src/sign.spec.ts (25)
  ✓ getSignedUrl (11)
    ✓ should maintain query params after signing a URL
    ✓ should include url path in policy of signed URL
    ✓ should sign a URL with a canned policy
    ✓ should sign a URL with a custom policy containing a start date
    ✓ should sign a URL with a custom policy containing an ip address
    ✓ should sign a URL with a custom policy containing a start date and ip address
    ✓ should allow an ip address with and without a mask
    ✓ should throw an error when the ip address is invalid
    ✓ should sign a RTMP URL
    ✓ should sign a URL with a policy provided by the user
    ✓ should sign a URL automatically extracted from a policy provided by the user
  ✓ getSignedCookies (8)
    ✓ should allow an ip address with and without a mask
    ✓ should throw an error when the ip address is invalid
    ✓ should be able sign cookies that contain a URL with wildcards
    ✓ should sign cookies with a canned policy
    ✓ should sign cookies with a custom policy containing a start date
    ✓ should sign cookies with a custom policy containing an ip address
    ✓ should sign cookies with a custom policy containing a start date and ip address
    ✓ should sign cookies with a policy provided by the user without a url
  ✓ getSignedUrl- when signing a URL with a date range (6)
    ✓ allows string input compatible with Date constructor
    ✓ allows number input in milliseconds compatible with Date constructor
    ✓ allows Date object input
    ✓ allows string input for date range
    ✓ allows number input for date range
    ✓ allows Date object input for date range

Test Files  1 passed (1)
     Tests  25 passed (25)
  Start at  14:58:42
  Duration  507ms (transform 133ms, setup 0ms, collect 135ms, tests 96ms, environment 0ms, prepare 87ms)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[kuhe]

there are two ends to the date range options, right? this needs to test the other end too.

[siddsriv]

nit: should we change this message to "....Ensure the date value is compatible with the Date constructor." instead of the "date string"