Improve REST API Swagger experience

[ivansenic]

I was trying to reproduce the issue from the #2373, by using the REST API swagger. However, it's the UI is not really user friendly.. Here are some suggestions:

• keyspaces names, as well as table names should be consistent in the examples and default parameter values.. Otherwise when in Try out mode user has to consistently change those names.. For example, in create keyspace the name of the keyspace in the example is killrvideo and then in many other places keyspace is cycling. we need to ensure that a flow like create keyspace -> get tables -> create table -> get/search rows -> add row works without altering the param values all the time
• create table example returns:

   {
     "description": "At least one partition key must be specified for table or materialized view 'cycling_events' [Column{name=emailaddress, type=text}]",
     "code": 500,
     "grpcStatus": null,
     "internalTxId": null
   }
  

• request body examples should be real swagger examples, so that I can correctly test them and not written as part of the endpoint description
• the order of the parameters should always be logical:
  • required parameters should be specified first
  • order of parameters should be logical, f.e. [keyspace, table, whatever]
  • example of current search endpoint (everything mixed):