Stumbled over this problem as well and can confirm the workaround via a ‘dummy’ component import class. An apparently independent analysis and confirmation of the workaround can be found in the accepted solution to Using conditions from bitbucket-web-common.
There is a long standing bug report for a slight variation of this (same underlying problem, slightly different missing component): BSERV-3810 When using Condition class in atlassian-plugin.xml, transitive dependency beans are not implicitly included