[full-ci] refactor: define either handler or route in editor actions, not both

[kulmann]

Description

Seems weird that we define both a handler for a button and a route for a router-link in editor actions. Let's see what CI says if we only define the one that's needed (route, with fallback to a handler when no route is available).

Related Issue

• Stumbled upon this in the process of fix: use a tag in context menu instead of button for editors in ctx menu #11854

Motivation and Context

hardening

How Has This Been Tested?

Perfect CI test coverage

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests
• Documentation
• Maintenance (e.g. dependency updates or tooling)

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud