Restrict having capabilities using the same name, even if they are different types

Problem Definition

Currently it is possible to have two capabilities using the same name, even if they are different types. For example, you can have the same name for a Command type capability called 'Fastlane' and a Fastlane capability called 'Fastlane' as well.

This can cause confusion when displaying or configuring the capabilities.

Suggested Solution

Restrict creating capabilities using the same name, regardless of their type.