feat(NODE-5613): add awaited field to SDAM heartbeat events

[durran]

Description

Adds an awaited field to server heartbeat events.

What is changing?

• Adds the awaited field and sets it to true when using the streaming protocol.
• Tests will come as part of NODE-5197

Is there new documentation needed for these changes?

None

What is the motivation for this change?

Need the field to pass tests coming in NODE-5197

Release Highlight

Server heartbeat events now contain an awaited field that is true when using the streaming protocol.

const client = new MongoClient(process.env.MONGODB_URI);
client.on('serverHeartbeatStarted', (event) => {
  console.log(event.awaited);
});
client.on('serverHeartbeatSucceeded', (event) => {
  console.log(event.awaited);
});
client.on('serverHeartbeatFailed', (event) => {
  console.log(event.awaited);
});

Double check the following

• Ran npm run check:lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[baileympearson]

We also need the awaited field on HeartbeatSucceeded and HeartbeatFailed events: https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.rst#events-api

[durran]

We also need the awaited field on HeartbeatSucceeded and HeartbeatFailed events: https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.rst#events-api

Good catch. I've updated.