Interaction handler keyboard handlers fix

[klakhov]

Motivation and context

Resolved #3536
The problem was caused by creating new Canvas() instance on each GET_JOB_SUCCESS action. Keyboard handlers are registered in constructor, so each new Canvas produces new handler.
It was solved by additional destroy() canvas method which emits canvas.destroy and svgjs destroy events. Interacton hanlder keyboard handlers are removed in case of such events.

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have added description of my changes into CHANGELOG file
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (read github docs)
• I have increased versions of npm packages if it is necessary (cvat-canvas,
  cvat-core, cvat-data and cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.
• I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

[ActiveChooN]

Please, add the canvas method to the README.md file and adjust package versions.