introduce helm-dependency-extra-args

[nazarewk]

What this PR does / why we need it:
TLDR; allows passing --skip-refresh to helm dependency build

Default behavior of helm dependency build is running equivalent of helm repo update before initiating packaging process.
This makes sense for handling a single repository - you always get the latest version even if you forget about running helm repo update yourself.

Passing --skip-refresh turns off the step allowing the user to run helm repo update once for the whole pipeline. The default behavior becomes redundant when handling a second chart in the same CI pipeline and becomes extremely wasteful when running build on large number of charts in a single pipeline.

ct lint invokes that default behavior for every single repository it checks, making it unnecessarily wasteful for it's primary use case. Sane default would be recommending ct users to invoke helm repo update before running ct lint, but that would be a breaking change.

This PR allows us to still invoke the proper behavior while preserving backwards compatiblity for ct users.

Which issue this PR fixes: fixes #368

Special notes for your reviewer:

Mocked test

I am not very proficient in mocking or Golang alltogether, but I believe TestLintYamlValidation works only by chance and my new TestLintDependencyExtraArgs contains proper invocation of Mock.On().

Basically I could not get the fakeMockLinter.AssertNumberOfCalls(t, "BuildDependenciesWithArgs", 1) to count occurences at all.

Submitted test is what I have determined to work empirically. When I ran the test twice with just a single .On() invocation it threw an error, invoking .On() followed by Repeatability = 1 allows a single call to the mocked method per test.

Introducing new method

I am not sure what is the project's external compatibility policy. I've added a fresh method to preserve backwards compatiblity when using ct as a library, since the struct is public.

[cpanato]

@nazarewk thanks for this PR, can you check the ci failures?

[nazarewk]

@cpanato This time it should pass (i've run go vet ./... && go test ./... locally), looks like it was not the right change before.

[cpanato]

@nazarewk thanks for the PR
can you generate the docs using the doc-gen? will be good as well to fetch the latest code from main

go build -o ct-bin ./ct/main.go

$ ./ct-bin doc-gen
Generating docs...
Done.

then commit the changes?
thanks!

[nazarewk]

@cpanato docs are generated

[cpanato]

@davidkarlsen can you take a look when you have some free cycle? thanks!

[davidkarlsen]

lgtm

[cep21]

This is a great PR for our CI/CD system. Looking forward to getting it in a released version!