chore(make): reorg build targets and add Azure

[jkoelker]

What problem does this PR solve?:

DRY up the current build targets by using pattern targets.

The basis is a build-${provider}-${distro}-${version} pattern target that will parse out the parts from the target name. Other pattern targets end up calling this target setting the various ADDITIONAL_OVERRIDES or ADDITIONAL_ARGS. They then provide the following pattern targets:

${provider}-${distro}-${version}_fips
${provider}-${distro}-${version}_offline
${provider}-${distro}-${version}_offline-fips
${provider}-${distro}-${version}_nvidia

All the existing targets are now just aliases to the dynamic pattern targets. In the future if we stay consistent with the image name pattern we have for aws/azure/vsphere, we won't have to have any alias patterns and can just setup CI to call the pattern targets directly.

I pulled the images targets out into their own makefile as well. The root one is getting kinda gnarly.

Adds Azure build using these this new target pattern.

Which issue(s) does this PR fix?:

*https://jira.d2iq.com/browse/D2IQ-85258

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[github-actions]

File	Coverage
All files	15%	❌
pkg/ansible/runner.go	0%	❌
pkg/app/artifacts.go	0%	❌
pkg/app/build.go	1%	❌
pkg/app/config.go	49%	❌
pkg/app/errors.go	0%	❌
pkg/app/provision.go	0%	❌
pkg/app/root.go	0%	❌
pkg/app/validate.go	0%	❌
pkg/appansible/io.go	0%	❌
pkg/appansible/playbook.go	0%	❌
pkg/azure/azure.go	0%	❌
pkg/logging/logger.go	0%	❌
pkg/packer/manifest.go	0%	❌
pkg/packer/packer.go	0%	❌
pkg/stringutil/rand.go	0%	❌
pkg/version/info.go	8%	❌

Minimum allowed coverage is 75%

Generated by 🐒 cobertura-action against 9e8ec95

[supershal]

Thanks for the refactoring code and make it extensible.