Restrict capability by attached block type

[BSick7]

Summary

Currently, a capability can be limited by app category (e.g. container, serverless, etc.). This is very helpful to prevent the wrong terraform modules from being used.

This could be improved with a filter on the app type. As we add Kubernetes support, there will be a need to differentiate between a capability that is deployed differently across platforms.

As an example, an Nginx Sidecar capability could be deployed to fargate and kubernetes, but requires totally different Terraform modules.