Parsing with Unix Timestamp tokens X/x and strict mode results in Invalid Date

[safareli]

Describe the bug

When x and X from dayjs/plugin/advancedFormat is used with strict mode parse fails:

dayjs(`/Date(${dayjs().format('x')})/`,"/[Date](x)/").format('/[Date](x)/')
> "/Date(1623787200000)/"
dayjs(`/Date(${dayjs().format('X')})/`,"/[Date](X)/").format('/[Date](X)/')
> "/Date(1623787200)/"

dayjs(`/Date(${dayjs().format('x')})/`,"/[Date](x)/",true).format('/[Date](x)/')
> "Invalid Date"
dayjs(`/Date(${dayjs().format('X')})/`,"/[Date](X)/",true).format('/[Date](X)/')
> "Invalid Date"

Expected behavior
last 2 examples should parse correctly as fist 2 cases do.

Information
tested on recent version of chrome (in dev tools of https://day.js.org/)

looks like related to:
#1467
#929
#1467

[iamkun]

🎉 This issue has been resolved in version 1.10.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[safareli]

Thanks for working on this @iamkun tho there is still has a bug. This example provided in this issue still returns Invalid Date. X/x tokens only work properly when they are used only without any other visual/escaped token in format.

I've open more specific issue for this #1569