[ruby] Add tests to operation servers in ruby client

[wing328]

• Add tests to operation servers in ruby client
• remove valid? (deprecated) from anyof model template

One will need to add the following entries to host table in order to test locally:

127.0.0.1   path.v1.test.openapi-generator.tech
127.0.0.1   path.v2.test.openapi-generator.tech
127.0.0.111 path.v3.test.openapi-generator.tech
127.0.0.1   operation.v1.test.openapi-generator.tech
127.0.0.1   operation.v2.test.openapi-generator.tech
127.0.0.111 operation.v3.test.openapi-generator.tech
127.0.0.1   server.v1.test.openapi-generator.tech
127.0.0.1   server.v2.test.openapi-generator.tech
127.0.0.111 server.v3.test.openapi-generator.tech
127.0.0.1   petstore.swagger.io

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/java*.
  For Windows users, please run the script in Git BASH.
• In case you are adding a new generator, run the following additional script :

  ./bin/utils/ensure-up-to-date
  

  Commit all changed files.
• File the PR against the correct branch: master (6.3.0) (minor release - breaking changes with fallbacks), 7.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

FYI @cliffano (2017/07) @zlx (2017/09) @autopp (2019/02)

[wing328]

docker tests failure not related to this change.