Standalone Validators support, modelname[] in body fix and globalDefinitions complience fix

[Lolotronop]

The main purpose of this PR is to add standaloneValidators support to elysia-swagger using t.Composite to merge schemas, fixing #218. t.Intersection was considered, but it seemed to generate much more complex schemas then was actually necessary

Of course, this wouldn't work with validator chains that don't make sense, like first checking that body is a t.String() in a standalone guard and then expecting it to be a t.Object() in a route, but those do not work in Elysia either. Currently, t.Composite ignores all non-object schemas when merging, so the resulting type for this example would be t.Object(). Alternative approach could be to check for non-object schemas in the validator chain and either throw an error or just return that schema to signal to the user that something is wrong, because most API's I assume expect objects, not plain values.

Along the way, this PR fixes .model support making it more spec compliant by deleting the $id property on the globalDefinitions and creating valid schemas for body: "modelname[]" definitions
The big test was updated to include all of these new behaviors

[walker-tx]

Howdy - it looks like this PR fixes 2 issues I'm currently experiencing:

• Model array isn't detected #197
• Invalid spec is generated using Elysia.Ref #209

Is this PR ready to merge? Looking forward to publishing my OAS via Elysia!

Update

I was wrong - my issues are a bit different than what's addressed here. But I'll submit a PR 👍🏻