Refactoring for RequestRetryPolicies and classes in exceptions.errors package

[wey1and]

Added refactoring for RequestRetryPolicies and classes in exceptions.errors package

Added new Exception called TarantoolNoSuchProcedureException for this message, so that the user can specify it in the retry policy

InnerErrorMessage:
code: 33
message: Procedure '*' is not defined

Closes #159

[akudiyar]

Mostly LGTM, but IT tests need more consideration.

[vrogach2020]

@wey1and please do not forget to include backwards compatibility changes into changelog

[ArtDu]

nit:
squash commits and make one commit message with list of what has changed. Either squash commits conveniently with a commit message. Because +459 −270 so hard to review without a general description or breakdown into commits.

One commit is expected before the merge with a full description for a simplified review and a clean commit history.

[ArtDu]

nit:

The PR title does not reveal what is in the PR. It seems better not to use the word refactoring, because there was not only a refactoring, but also changes in API of the exceptions.errors package. And since the external behavior of the code will change, then you can not use this word, it seems better to use a CHANGE or something like that.

Just this will be a generalized version of what is happening in PR. And in the description, you can just write that a refactoring has taken place, the API has changed and a new exception has been added and why it was added. And I expect to see this also in the final squashed commit message.

[ArtDu]

LGTM

[akudiyar]

LGTM.

BTW there is a truncate_space() test failing on 1.10 -- we need to fix it.

[vrogach2020]

@akudiyar Created an issue on truncate
#164