Integrate dmn-js@17 / diagram-js@15 (implicit keyboard binding)

[nikku]

Proposed Changes

Update to latest diagram-js and dmn-js versions.

Incorporates implicit keyboard / focusable canvas.

Child of https://github.com/bpmn-io/internal-docs/issues/1081.

Checklist

To ensure you provided everything we need to look at your PR:

• Brief textual description of the changes present
• Visual demo attached
• Steps to try out present, i.e. using the @bpmn-io/sr tool
• Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

[barmac]

I tested this locally, and apparently undo/redo shortcut does not work in dmn-js@17 but it works in dmn-js@16.

[barmac]

Oh ok, this is due to bpmn-io/dmn-js#920

[jarekdanielak]

@barmac ready for review.

[barmac]

Suggested change

	* Keyboard is now implicit, and canvas is focusable, cf. [bpmn-io/diagram-js#662](https://github.com/bpmn-io/diagram-js/pull/662))
	* Keyboard is now bound implicitly, and canvas is focusable, cf. [bpmn-io/diagram-js#662](https://github.com/bpmn-io/diagram-js/pull/662)). Calls to `keyboard.bind` and `keyboard.bindTo` now result with a descriptive console error and have no effect.

[jarekdanielak]

Actually not all new calls to bind will result in an error. Proposed a better message in a4faee3

[barmac]

Let's update camunda-bpmn-js changelog in that case: https://github.com/camunda/camunda-bpmn-js/blob/main/CHANGELOG.md#breaking-changes

[nikku]

To be clear: I'd like us to anchor at "do not use these APIs anymore", rather than "you can continue to use them.

I think the old changelog entries + descriptive error on mis-use were OK already. To simplify this message it could read:

* Keyboard is now bound implicitly, and canvas is focusable, cf. [bpmn-io/diagram-js#662](https://github.com/bpmn-io/diagram-js/pull/662)). Attempts to bind the keyboard to an explicit HTML element have no effect.

[barmac]

Giving we have an issue for the limitation from bpmn-io/dmn-js#921 (review), this is ready to merge.