1. Add a service based on Spring Boot to support the test of sink table.

1. The DDL of source table should be like:
   CREATE TABLE UserScores (name STRING, score INT)
   WITH (
   'connector' = 'http-restful',
   'mode' = 'source'
   'format' = 'http-restful-json'
   'remote-url' = 'http://localhost:8088/some/re?name={#name}',
   'remote-body' = '{name: '{#name}' }'
   'source.request.body-format' = '{"token":"some token","data":DATA}'
   'source.request.headers.Cookie' = '_ga=GA1.2.2136019336.1646989403'
   'source.request.headers.Referer' = 'https://www.baidu.com'
   'source.request.headers.xxx' = 'yyyy'
   );

2. The DDL of sink table should be like:
   CREATE TABLE UserScores (name STRING, score INT)
   WITH (
   'connector' = 'http-restful',
   'mode' = 'sink'
   'remote-url' = 'http://localhost:8088/some/re',
   'format' = 'http-restful-json'
   'sink.request.body-format' = '{"token":"some token","data":DATA}'
   'sink.request.headers.Cookie' = '_ga=GA1.2.2136019336.1646989403'
   'sink.request.headers.Referer' = 'https://www.baidu.com'
   'sink.request.headers.xxx' = 'yyyy'
   );

Ref:

1. https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#server_error_responses`

Support PUT AND DELETE by id on both source and sink side where id should be indicated in URL.

Only support at most once on source side because the source side is not a queue that can be consumed from at some point again. On the sink side, it is idempotent because it is restful API which means the result will be the same how matter how many time the PUT/DELETE are sent.

Like JDBC SQL connector, and Elasticsearch SQL connector, the Http Restful SQL connector can operate in upsert mode for exchanging UPDATE/DELETE messages with the external system using the primary key defined on the DDL.

If no primary key is defined on the DDL, the connector can only operate in append mode for exchanging INSERT only messages with external system.
Dependencies #