Using isBetween from Invalid Date return true when using '[]' as a 4th parameter

**Describe the bug**
Found this bug when accidentally put null to constructor.
```
dayjs(null).isBetween(dayjs('2022-01-28'), dayjs('2022-02-28'), 'day', '[]'); // returns true;
dayjs('random string').isBetween(dayjs('2022-01-28'), dayjs('2022-02-28'), 'day', '[]'); // returns true;
dayjs('random string').isBetween(dayjs('2022-01-28'), dayjs('2022-02-28'), 'day', '[)'); // returns false;
dayjs('random string').isBetween(dayjs('2022-01-28'), dayjs('2022-02-28'), 'day', '(]'); // returns false;
dayjs('random string').isBetween(dayjs('2022-01-28'), dayjs('2022-02-28'), 'day', '()'); // returns false;

dayjs('2022-01-27').isBetween(dayjs('2022-01-28'), dayjs('2022-02-28'), 'day', '[]'); // returns false;
```

**Expected behavior**
Invalid Date should always return false when using isBetween

**Information**
- Day.js Version [e.g. v1.0.0]: latest (tested on dayjs homepage)
- OS: [e.g. iOS] macOS
- Browser [e.g. chrome 62] Chrome 106
- Time zone: [e.g. GMT-07:00 DST (Pacific Daylight Time)] UTC+9

Reproduce the provided isBetween examples with invalid dates and each inclusivity parameter. Start at the isBetween entry point and trace how invalid dates and the '[]' bounds are evaluated. Done means invalid dates consistently return false, with tests covering the reported cases.

Written by the indexing model from the issue text.