chore(ci): drop support for server 4 & 5 from CI and mark 6 as EoL COMPASS-9896

[mabaasit]

Description

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• If this change updates the UI, screenshots/videos are added and a design review is requested
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[Copilot]

Pull Request Overview

This PR removes CI testing support for MongoDB server versions 4.4.x and 5.x.x, and moves version 6.0.x from the maintained versions to end-of-life (EoL) status in the CI configuration.

• Removes all test tasks for MongoDB server versions 4.4.x and 5.x.x (both community and enterprise editions)
• Moves MongoDB 6.0.x versions from maintained to end-of-life category
• Updates CI build variants to reflect the new server version support matrix

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.evergreen/buildvariants-and-tasks.yml	Removes 276 lines of test task definitions for server 4.4.x and 5.x.x versions, and moves 6.0.x tests from maintained to EOL build variant
.evergreen/buildvariants-and-tasks.in.yml	Updates the server version arrays by moving 4.4.x and 5.x.x to removal and 6.0.x from maintained to EOL categories

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[nbbeeken]

Are there any tests that are filtered to run on these server versions that are no longer relevant?

I can see functionality that is no longer relevant (linked) should we be scanning for things like that and removing them?

compass/packages/compass-indexes/src/components/regular-indexes-table/regular-index-actions.tsx

Line 35 in a393f8d

const MIN_HIDE_INDEX_SERVER_VERSION = '4.4.0';

[gribnoysup]

should we be scanning for things like that and removing them?

Specifically for functionality the answer is "No", the plan is to not deliberatly degrade the experience or break the behavior for older versions when we "drop" support, unless something forces us to

[nbbeeken]

Gotcha, although keep in mind that driver upgrades will just prevent connecting to older server versions at some point:

Current experience when connecting to 4.0

Uncaught:
MongoServerSelectionError: Server at localhost:2390 reports maximum wire version 7, but this version of the Node.js Driver requires at least 8 (MongoDB 4.2)

So maybe that will be the forcing function to go and clean up old functionality?

[mabaasit]

Gotcha, although keep in mind that driver upgrades will just prevent connecting to older server versions at some point:

TIL. Yeah eventually driver will catch such things.