Handle Vite 5 types changes

[bluwy]

Vite 5 removes the https: boolean type and as it doesn't have much use by default. A plugin or manual configuration is always needed for https to actually work (e.g. certs). (vitejs/vite#14681)

This PR updates the types breaking change caused by it. It uses @ts-ignore so it works on both Vite 4 and 5. The as any is also needed so the config hook doesn't error by TS due to incorrect type returned by the function.

---

Extra notes unrelated to PR

It seems like before (Vite 4), users could do vite --https or https: true in vite.config.js to get the right certs generate by laravel-vite-plugin. In Vite 5, this isn't possible anymore except if https: {} in vite.config.js. Though it isn't quite exactly documented in the laravel docs.

Just want to note this in case you want to handle this differently in the future. For example, the detectTls could be used to enable https internally. Right now it doesn't due to the existing logic here:

vite-plugin/src/index.ts

Lines 163 to 166 in 7abca67

	https: userConfig.server?.https === false ? false : {
	...serverConfig.https,
	...(userConfig.server?.https === true ? {} : userConfig.server?.https),
	},

[gabrielrbarbosa]

#253

[timacdonald]

Really appreciate you sliding into our Laravel plugin, @bluwy, to help get us ready for Vite 5 ❤️

I've take the changes here and added them to our single PR to upgrade to Vite 5. I'll close this one off, but thank you so much.

We are also gonna drop Vite 4 support, so it should make things a little smoother with type changes.

[bluwy]

No problem! 👍