[Feature Request] ct.yaml override per chart

[dirtycajunrice]

Currently, if you have a ct.yaml you must define it in a single place and pass it to the action. If any chart has a unique requirement this becomes problematic. Examples would be if a chart is a library, or if a chart had required defaults that are not set in the values.yaml file.

[cpanato]

you can solve that by adding some flows or tests in the ci job itself.