align `type` notation for access and input

[fabianburth]

Description
While reviewing the component authoring PR, I've noticed that our type system notation is all over the place.

Sometimes we use versioned lower case helm/v1 (for input), sometimes we use unversioned upper case Helm (for access) (they are not the only examples). We need to converge this to one standard notation throughout our documentation.

Partially related to #961.

We want to use k8s UpperCamelCase/v1 typing style as the default notation.
Update type notation in code and test examples to keep it aligned.

Done Criteria

• Code has been reviewed by other team members
• Analysis of existing tests (Unit and Integration)
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
• Enduser Documentation updated (if applicable)
• Internal technical Documentation created/updated (if applicable)
• Successful demonstration in Review