allow custom git clone flags during a plugin checkout

[scriptnull]

Is your feature request related to a problem? Please describe.
In all our jobs, the first thing to be executed is the "Preparing plugins" section which clones the git repos of plugins that we use for that step.

But the git clone of a plugin repo is adding a lot of log lines (to report the progress of the clone) which often adds noise to our build logs. We would ideally like to suppress these logs by doing a git clone --quiet instead.

Describe the solution you'd like
I would like to add a new config to the agent - something like plguins-git-clone-flags (BUILDKITE_PLUGINS_GIT_CLONE_FLAGS) and make use of that config while cloning the plugin repo here:

agent/bootstrap/bootstrap.go

Lines 899 to 916 in 79a7ba7

	args := []string{"clone", "-v"}
	if b.GitSubmodules {
	// "--recursive" was added in Git 1.6.5, and is an alias to
	// "--recurse-submodules" from Git 2.13.
	args = append(args, "--recursive")
	}
	args = append(args, "--", repo, ".")
	// Plugin clones shouldn't use custom GitCloneFlags
	err = roko.NewRetrier(
	roko.WithMaxAttempts(3),
	roko.WithStrategy(roko.Constant(2*time.Second)),
	).Do(func(r *roko.Retrier) error {
	return b.shell.Run(ctx, "git", args...)
	})
	if err != nil {
	return nil, err
	}

Describe alternatives you've considered
None

Additional context
This is how our build logs look when the plugin is cloned for the first time. (a sample of first few lines, but imagine 500+ more lines like this)

Having this config option would help is in avoiding these lines in our build logs.

[scriptnull]

I am willing to open a pull request for this if someone from the buildkite team could tell me if it is okay to add the above-proposed config option 🙂