fix: Use Record<string, unknown> instead of {} notation when no properties are found

[Traxmaxx]

I also tried to create an test-case for this scenario, but the current test suite fails in two instances with:

E                     items:
E                       description: Uniform Resource Name
E                       example: urn:pm:service::foobar/d9a6fc2e-a4b3-4fba-9f20-c5bd2fdb5071
E         -             pattern: ^urn:[\w-]+:[\w.-]*:[\w.-]*:[\w-]+\/[\w:-]+$
E         ?                                                            ^^^
E         +             pattern: ^urn:[\w-]+:[\w.-]*:[\w.-]*:[\w-]+\/[^\/]+$
E         ?                                                           + ^
E                       type: string

The pattern seems to expect /[\w:-]+$ but receives /[^\/]+$ in the regular expression 🤔
I wasn't sure if that is correct or if this test case is borked on my machine.

All of the above was addressed. PR is ready for review : )

[fabfuel]

please add the trailing line-break

[Traxmaxx]

Woops, I updated my Editor config to always make sure there is a new line. Thank you!

[fabfuel]

Woohoo, 1st PR @Traxmaxx! Just this tiny line-break and we can merge 🙌