refactor: rename args -> parameters, resolve -> configure

[awphi]

Changes

Attempts to have a stronger opinion about naming in the paramaterisation bit of the codebase as it's quite muddy atm (e.g. many uses of the term 'resolved', lots of references to 'args'/'arguments' which we don't use anymore):

• Renamed the internal package from arguments to parameter. The singular gives its exports more natural names i.e. "parameter provider", "parameter values"
• Replaced argument terminology with Definition, Values, and parameter-focused errors. This ditches one use of the term 'resolved'. Values is a simplification that avoids the conversion from map->array->map we had before.
• Kept “args” only for CLI arguments and Docker build.args.
• Renamed the overall workflow to project.Configure, ditching one usage of the word 'resolve'/'resolved'
• Replaced ambiguous “resolved” checks in the strict provider chain with hasValue et al. Ditches the final use of 'resolved'

Big PR I know but it's almost pure renaming and split up by commit fairly well imo. Please push back if you start reviewing and disagree!

Checklist

• 🤖 This change is covered by tests as required.
• 🤹 All required manual testing has been performed.
• 📖 All documentation updates are complete.

[muchzill4]

I'm not sure if we should rename the package. We should definitely update the signatures though.

Providers are responsible for turning params into args:

func (p *CLIProvider) Provide(params []Param) ([]Arg, error) {

Frankly, I'd rather the package was still arguments, not parameters. I.e.: named after what it provides, not what it takes as an argument.