Fix move interactivity schema to supports property instead of selectors property

[fabiankaegy]

What?

Moves the interactivity subproperty from the selectors property to the supports

Why?

Because the property is a block support option. It was missplaced before.

How?

By copying it to the correct spot.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: fabiankaegy <fabiankaegy@git.wordpress.org>
Co-authored-by: gziolo <gziolo@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Flaky tests detected in f69f2d6.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7955660862
📝 Reported issues:

• [Flaky Test] can add submenus #50976 in /test/e2e/specs/editor/blocks/navigation-list-view.spec.js
• [Flaky Test] list view should correctly reflect navigation items' structure #58980 in /test/e2e/specs/editor/blocks/navigation-list-view.spec.js

[gziolo]

Good catch. Aside: the verification in integration tets for core blocks and the block supports in the schema doesn’t seem to strict as it didn’t help to catch this mistake.

[fabiankaegy]

@gziolo yeah I'm pretty sure that is because the supports property has the additional properties option allowed. So anything is valid there.