Reduce use of write concern timeout in tests

[kevinAlbs]

Summary

Do not set write concern timeout in most tests executing server operations.

Background & Motivation

Intended to fix recent observed failures in Evergreen. Example:

FAIL:/Users/ec2-user/data/mci/ffb7ebf283ddea39b3d6257ed6eff9b4/mongoc/src/libmongoc/tests/test-mongoc-client-side-encryption.c:76  _before_test()
  ret
  waiting for replication timed out; Error details: { wtimeout: true, writeConcern: { w: "majority", wtimeout: 1000, provenance: "clientSupplied" } } at sh01

I expect the 1 second timeout is sometimes too short (IIRC servers on macOS Evergreen hosts generally run slower).

Removing wTimeout is expected to mean "no timeout". Quoting docs:

If you do not specify the wtimeout option and the level of write concern is unachievable, the write operation will block indefinitely. Specifying a wtimeout value of 0 is equivalent to a write concern without the wtimeout option.

Exceptions:

• Two tests in test-mongoc-sample-commands.c keep their wTimeout. These are used as documentation examples and intended to match the descriptions of DRIVERS-547 and DRIVERS-655.
• Files in src/libmongoc/examples are left as-is. The examples are not run in Evergreen.

References:

• PyMongo tests for CSFLE do not use a wTimeout.

[eramongodb]

Should these also be updated?

mongo-c-driver/src/libmongoc/src/mongoc/mongoc-write-concern.c

Lines 466 to 468 in 0540e99

	/* mongoc_write_concern_set_wmajority() only assigns wtimeout if
	* it is >= 0. Since we set wtimeout below, pass -1 here. */
	mongoc_write_concern_set_wmajority(write_concern, -1);

mongo-c-driver/src/libmongoc/tests/test-mongoc-cursor.c

Line 142 in 0540e99

mongoc_write_concern_set_wmajority(write_concern, 1000);

[kevinAlbs]

Should these also be updated?

mongo-c-driver/src/libmongoc/src/mongoc/mongoc-write-concern.c

Lines 466 to 468 in 0540e99

	/* mongoc_write_concern_set_wmajority() only assigns wtimeout if
	* it is >= 0. Since we set wtimeout below, pass -1 here. */
	mongoc_write_concern_set_wmajority(write_concern, -1);

Updated to use mongoc_write_concern_set_w(write_concern, MONGOC_WRITE_CONCERN_W_MAJORITY); to simplify. No behavior change is expected, but it removes the unused -1 timeout.

Removed another instance of an unnecessary 0 timeout in client-side-encryption-server-schema.c

mongo-c-driver/src/libmongoc/tests/test-mongoc-cursor.c

Line 142 in 0540e99

mongoc_write_concern_set_wmajority(write_concern, 1000);

Kept as-is since the test later checks the timeout is 1000.