Moved ClusterParser exceptions to BaseParser class

[vladvildanov]

Pull Request check-list

Please make sure to review and check all of these items:

• Do tests and lints pass with this change?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?
• Was the change added to CHANGES file?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

If RESP3 is enabled, the ClusterParser becomes immediately overridden with _RESP3Parser which leads to the fact that all additional exceptions isn't handled by cluster implementation.

ClusterParser class shouldn't exist and inherit other parsers just to extend a list of exceptions that should be associated with given error codes. Parsing errors and associate them to exception classes is a responsibility of parsers itself regardless of server topology, potentially you could get any error code as a response from server and parser should be aware of it.

[uglide]

LGTM, but why do you think it's a breaking change? I see no changes affecting public API

[vladvildanov]

@uglide Well, from my POV it isn't, just the fact that public class was removed makes me feel it would be wise to consider this as a breaking change

[uglide]

Ah, I see. Good then.