Improve documentation/process of writing component yaml files

[Ruwann]

When writing the fondant_component.yaml file, I ran into issues where sometimes types such as int32 are needed, while in other places just a regular int. It would nice to have better documentation on what is expected in which place.
Also, I'm not sure if there are guidelines on deciding between int16, int32, ...

Some things that could be discussed as part of this:

• Make it more visible in the documentation or create a separate section for it.
• It's possible to have VS Code validate and generate help on hover based on a jsonschema (which are already used by fondant under the hood), this still requires setup from the user but makes it easier at least when writing these yaml files:
• Expose the validation functionality separately, e.g. via CLI so you can easily validate a component spec yourself