Proposal: runners should not appear as "locked" when their type is `group` or `instance`

Background

The "locked" runners setting only applies to specific runners.

Problem

Only when runners are of the "specific" (project) type, the "locked" setting makes sense. However, "group" runners still appear as "locked", causing confusion:

Furthermore, in some situations, the "shared" (specific) runners can be set to "locked" via the API even though this change has no effect.

Proposal

Only "specific" (project) runners should show as locked (depending on their configuration).

A component:label type warning for locked should be placed in the type/state column of the Runner table.

Technical Info

Currently, the MR Conditionally render runner locked badges, conditionally renders the locked badge when a runner object has group_type? and instance_type? set to false.

Instead, the runner object should always return locked? = false when it is a group_type or instance_type, since the notion of locked is not applicable in the context of group or shared runners.