Robotframework-requests

This is mainly an internal maintenance release, no new features or fixes are visible.
Mainly GitHub workflow changes, code linting and documentation.

Those are the merged pull requests:
272 Migrated from Travis to GitHub Action, fixed flake8 errors
269 268 Improved documentation
266 Fixed workflow for draft release

This is mainly an internal maintenance release, no new features or fixes are visible.
Mainly code and tests have been split and moved to different files.

Those are the merged pull requests:
263 Code cleanup
262 Pypi publish on new release
265 Fix deprecation warnings on internal flask server

Fixed 259

What's new
Status Should Be
Fails if response status code is different than the expected.
``expected_status`` could be the code number as an integer or as string.
But it could also be a named status code like 'ok', 'created', 'accepted' or 'bad request', 'not found' etc.
The ``response`` is the output of other requests keywords like ``Get Request``.
A custom message ``msg`` can be added to work like built in keywords.

Request Should Be Successful
Fails if response status code is a client or server error (4xx, 5xx).
The ``response`` is the output of other requests keywords like ``Get Request``.
In case of failure an HTTPError will be automatically raised.

Local HTTP Test Server
A local version of flask httpbin server has been integrated in the project for testing purpose.

What's new

Enhanced log
- parameters of requests are now dynamically handled
- headers defined in session are now shown in logs
- response is logged if standard python/robotframework debug level is enabled (might be verbose)

Retry on specific status codes
- is now possible to retry the request even for specific response code (eg 502, 503)
- it is also possible to specify for which method the retry is allowed

This release covered some maintenance on build and tests.
- deprecated keywords have been removed
- duplicated code have been managed
- documentation have been updated a bit