feat: migrate back to Vanilla-Calendar-Pro

[ghiscoding]

• migrate to vanilla-calendar-pro and drop the custom fork vanilla-calendar-picker (which was always meant to be temporary) that I had created until all features I needed were going to be merged into the original project Vanilla-Calendar-Pro and we are just about to be there.
• NOTE: the Types are not imported the same way, they must be imported from 'vanilla-calendar-pro/types' instead of the default import

[stackblitz[bot]]

Run & review this pull request in StackBlitz Codeflow.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.8%. Comparing base (14c04d7) to head (8e025e2). Report is 10 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #1644 +/- ## ======================================= Coverage 99.8% 99.8% ======================================= Files 198 198 Lines 21849 21849 Branches 7306 7023 -283 ======================================= Hits 21786 21786 Misses 63 63 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[ghiscoding]

Vanilla-Calendar-Pro now has all features and fixes that I had in my fork, so we can now officially switch back to that repo.. woohoo 🎉