feat(deadline): DocumentDB engine version support upgraded upto v5.0

[sakshie95]

Problem
Only documentDB engine version 3.6 was supported before current Deadline release 10.3.1.3. With the MongoDB and DocumentDB version upgrades to 5.0 all versions (3.6, 4.0, 5.0) are supported with Deadline. We need to relax constraints on engine version 3.6 that exist in RFDK

Solution
Upgraded engine version support to all versions prefix with 3.6, 4.0 or 5.0 as per the compatibility now. Updated relevant documentation in the code as well. Removed a Unit Test case testing the engine version constraint to 3.6. Since there are no other versions of DocumentDB available we need not add this test case with a different parameter.

Testing

1. yarn build:

aws-rfdk: =============================== Coverage summary ===============================
aws-rfdk: Statements   : 97.93% ( 3316/3386 )
aws-rfdk: Branches     : 95.08% ( 1045/1099 )
aws-rfdk: Functions    : 96.98% ( 514/530 )
aws-rfdk: Lines        : 98.09% ( 3196/3258 )
aws-rfdk: ================================================================================
aws-rfdk: Test Suites: 62 passed, 62 total
aws-rfdk: Tests:       1277 passed, 1277 total
aws-rfdk: Snapshots:   0 total
aws-rfdk: Time:        240.366 s

2. Deployed the All-In-Infrastructure-SEP stack in my AWS account with default engine version set to 3.6, confirmed it spun up and tore down successfully.

3. Manually updated the default version of DocDB to 5.0 and deployed the All-In-Infrastructure-SEP stack with the updated engine version to validate it works fine.

4. Ran the integration tests using my AWS account as well. Validated that they run fine.

Test Suites: 1 passed, 1 total
Tests:       21 passed, 21 total
Snapshots:   0 total
Time:        35.8 s, estimated 44 s
Ran all test suites matching /deadline_01_repository.test/i.
Test results written to: .e2etemp/deadline_01_repository/test-report.json

[ddneilson]

Aside, we should also add the ability for the user to select their DocumentDB engine version when using the defaults in the Repository construct.

[jericht]

I agree with Daniel's comments. Ready to approve once both of those are addressed.

[sakshie95]

Aside, we should also add the ability for the user to select their DocumentDB engine version when using the defaults in the Repository construct.

Discussed this offline with @ddneilson. This is a feature that would need a data migration strategy for the customers to migrate their data from older version to a newer version which they can choose. Logged a backlog item for this

[sakshie95]

I agree with Daniel's comments. Ready to approve once both of those are addressed.

Addressed & resolved both comments!