v3 uses generics in schemas so IDEs can see instance and property base types

[spacether]

v3 makes all schema classes based on Generic[T]
So now when models are instantiated, they will show what class they are based on
Like so:

my_model = MyModel(some_str='a')
# my_model is type MyModel[frozendict.frozendict] in the vscode IDE
# my_model.some_str is type SomeStr[str] in the vscode IDE

• keep the mixin classes for ide methods (needed to show possible properties)
• make Schema generic
• when making classes always define new so the generic can be seen
• update properties to add the generic type
• var equals class define class instead, needed for generics
• update ref props to add generic
• fix UnsetAnyTypeSchema not being used in AbstractStepMessage
• update get_item property with type
• update get_item array with type
• add __init__ method to AnyTypeSchema
• update parameter and header schema and content type definition to be [typed]
• change ref schemas to be type aliases

Out of scope future improvement. Use typing.Never in NotAnyType

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/python*.
  For Windows users, please run the script in Git BASH.

[spacether]

Closing this and work will continue on in #174
Starting a new PR was easier than rebasing this one