standardize references from "mongodb-enterprise" to "mongodb-kubernetes

[nammn]

Summary

This pull request primarily focuses on renaming resources and references from "mongodb-enterprise" to "mongodb-kubernetes" across the codebase. The changes ensure consistency in naming conventions and align with the updated project branding. Below are the key changes grouped by theme:

Resource and Binary Renaming

• Updated the output binary name in Makefile from mongodb-enterprise-operator to mongodb-kubernetes-operator.
• Changed the command in manager.yaml to use /usr/local/bin/mongodb-kubernetes-operator instead of /usr/local/bin/mongodb-enterprise-operator.
• Updated the Helm chart template to reflect the new binary name mongodb-kubernetes-operator.

Repository and Documentation Updates

• Updated repository links in various files (e.g., release.md, contributing.md, README.md) to point to https://github.com/mongodb/mongodb-kubernetes instead of https://github.com/mongodb/mongodb-enterprise-kubernetes. [1] [2] [3]
• Adjusted references in README.md for the database Docker image to use mongodb-kubernetes-database in place of mongodb-enterprise-database. [1] [2] [3]

Dockerfile Adjustments

• Updated Dockerfiles to copy licenses and binaries for mongodb-kubernetes instead of mongodb-enterprise. [1] [2] [3]
• Renamed directories and paths in Docker-related files to align with the mongodb-kubernetes naming convention. [1] [2]

Inventory and Image Naming

• Updated image registry paths in inventory files (e.g., database.yaml, test.yaml) to use mongodb-kubernetes instead of mongodb-enterprise. [1] [2] [3] [4]

Miscellaneous

• Modified the generate_ssdlc_report.py script to use mongodb-kubernetes for image names, except for "ops-manager" which retains its original naming convention.
• Removed the unused e2e-inventory.yaml file from the mongodb-community-operator directory.

These changes collectively ensure consistency in naming and branding across the project while removing outdated references to "mongodb-enterprise."

Proof of Work

• green ci

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you checked for release_note changes?

Reminder (Please remove this when merging)

• Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
• Our Short Guide for PRs: Link
• Remember the following Communication Standards - use comment prefixes for clarity:
  • blocking: Must be addressed before approval.
  • follow-up: Can be addressed in a later PR or ticket.
  • q: Clarifying question.
  • nit: Non-blocking suggestions.
  • note: Side-note, non-actionable. Example: Praise
  • --> no prefix is considered a question

[nammn]

evergreen retry

[mircea-cosbuc]

LGTM

[mircea-cosbuc]

@lucian-tosa Comments were addressed in 4291950 , please take another look.