[Feature]: Recipes should warn/error on missing component dependencies

## Problem / motivation
Today, when creating a component, the user has the ability to assign other components as dependencies. This makes sense, since that's needed for testing to pass. When creating a recipe, it's not clear if those dependencies will be included as part of the recipe, or should the user add those manually.

## Proposed solution
The recipe builder should warn if a dependent component is not included in a recipe. That makes the intention clear that the user is responsible for all components feeding into a recipe.

## Alternatives considered
Since we know what dependencies are required by a specific component, we could add those dependencies to be included, automatically, when adding a component to a recipe. I do understand this leads to larger issues when different components use different versions of the same dependency, so Im guessing this is not the best solution.

## Additional context
Say we have:
Component A: simple small requirement package
Component B: Requires component A to function

When creating a recipe and only Component B is added, display "Some components are missing dependencies"

It could 100% be the case that I'm missing something in this flow, so let me know please

Start by locating the recipe builder and the existing component dependency validation or tests. Trace how selected components and their dependencies are determined. Done means a recipe that omits a required dependency displays a missing-dependencies warning or error, while a recipe containing all dependencies does not.

Written by the indexing model from the issue text.