component.yaml should probably have the component's `version` in it

Remotely, a component's version is only inferable from looking at OCI-isms (namely, annotations on the image).
Locally, it's only inferable from looking at the parent directory of the component.

That's not very ideal, especially if one day we want to allow hosting components at HTTP urls instead of OCI

Start by locating the component.yaml handling and the code that currently infers versions from OCI annotations or the parent directory. Determine how a version field should be represented and consumed for both remote and local components; done means the component version is available from component.yaml in both cases.

Written by the indexing model from the issue text.