fix(swagger): fix resolved path in windows OS context

[Romakita]

Closes: #2692

[github-actions]

Benchmarks

• Machine: linux x64 | 4 vCPUs | 15.6GB Mem
• Node: v18.20.2
• Run: Fri May 03 2024 09:21:01 GMT+0000 (Coordinated Universal Time)
• Method: autocannon -c 100 -d 10 -p 10 localhost:3000 (two rounds; one to warm-up, one to measure)

	Version	Router	Requests/s	Latency	Throughput/Mb
koa	2.13.4	✗	35090.2	27.97	6.26
tsed-koa	7.68.3	✓	12057.8	82.19	10.21
express	4.19.2	✓	10832.4	91.51	1.93
express-injector	4.19.2	✗	9937.1	99.64	2.27
nest	8.4.3	✓	9533.8	103.81	2.29
tsed-express	7.68.3	✓	9045.6	109.59	1.66
express-morgan	4.19.2	✗	5671.5	174.60	1.01
fastify-big-json	3.29.4	✓	N/A	N/A	N/A
fastify-injector	3.29.4	✓	N/A	N/A	N/A
fastify	3.29.4	✓	N/A	N/A	N/A
nest-fastify	8.4.3	✓	N/A	N/A	N/A

Explanation

The benchmark shows a performance difference between the frameworks. We note that Ts.ED is often last. In fact, Ts.ED uses features useful to a production application which reduce its performance.

For example, Ts.ED initializes a sandbox (async_hook) for each request in order to work in an isolated context if necessary.
It also initializes the elements necessary for monitoring requests in a log manager.

All this at a necessary cost that reflects the reality of a production application ;)

[VictoriqueMoe]

tried this branch locally and works on win

[Romakita]

🎉 This PR is included in version 7.68.5 🎉

The release is available on:

• v7.68.5
• GitHub release

Your semantic-release bot 📦🚀