Description

Implement SDAM logging per spec guidelines (except those affected by DRIVERS-2711.

Use Case

As a... Node user
I want... to log SDAM events when logging >= debug level
So that... I can see which SDAM events are taking place in my code paths 

User Impact

• None - Logging will not be released until NODE-5672

Unknowns

• None

Acceptance Criteria

Implementation Requirements

• Add relevant spec files to the driver, from the DRIVERS-1670 commit
• Implement all log messages described in spec
  • "Starting Topology Monitoring"
  • "Stopped Topology Monitoring
  • "Starting Server Monitoring"
  • "Stopped Server Monitoring"
  • "Topology Description Changed"
  • "Server Heartbeat Started"
  • "Server Heartbeat Succeeded"
  • "Server Heartbeat Failed"
• Log all messages a debug level, for component topology
• Add support for SDAM events in spec runner

Testing Requirements

• Ensure driver passes relevant unified spec tests
  • Except tests affected by DRIVERS-2711, will be run separately, (since the Node driver's current behavior is no TopologyDescriptionChangeEvent publishing on Topology.CLOSE, which contradicts certain spec tests)
• Unit Tests TBD - will see if needed as implemented

Documentation Requirements

• N/A