Ensure software definitions are complete and can be built in isolation

What does this MR do?

Ensure each software component can be built in isolation

- Update all software definitions to build independently
- ruby-grpc was excluded from this iteration because it
  would force gitlab-rails and gitaly to build earlier
  lowering efficiency by dirtying the cache too often

Related https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/596

Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>

Ensure every software definition can be built in isolation.

Related issues

gitlab-org/distribution/team-tasks#596 (comment 891531141)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

• Merge Request Title, and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com
• Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
• trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• Documentation created/updated
• Tests added
• Integration tests added to GitLab QA
• Equivalent MR/issue for the GitLab Chart opened