• Implement Ignore-Removed-Shards operation mode support in CollectionChangeStreamShardTargeterImpl module based on the design.
• Add a smoke test.
• Disable removed shard check at  https://github.com/10gen/mongo/blob/5cfd14aa58b6f3f547a83de29b65a169d96184e5/src/mongo/db/pipeline/sharded_agg_helpers.cpp#L964-L973 for v2 change streams.

Suggested smoke test scenario:

1. Open a change stream in Strict mode to get the resume token resumeToken.
2. Create and shard a collection Coll; allocate collection to shard set {A, B}.
3. Insert documents into the collection Coll so the documents are distributed in shards A and B.
4. Reshard collection Coll and allocate to shards {B, C}.
5. Insert some documents into collection Coll.
6. Remove and decommision shard A from the system.
7. Open a change stream on collection Coll in Ignore-Removed-Shards mode from resume token resumeToken and read all events. Verify that all events were returned except the ones recorded on shard A.

Reuse as much of the test script from jstests/sharding/query/change_streams/change_stream_v2_smoke.js.