Add time based flush + add force telemetry flag

[samikshya-db]

Description

• We should be sending out telemetry in 3 cases :
  • When batch size reaches a threshold (Already implemented ✅ )
  • When connection/statement is closed (Already implemented ✅ )
  • When time since last telemetry export reaches threshold (In this PR 🚧 )
• Add a force telemetry flag : this will turn on telemetry even when server flag say otherwise. This will be useful when :
  • Internal use-cases need to be laced with telemetry (eg: benchmarking)
  • Force telemetry for customers facing issues : for us to be able to debug better.

Testing

• Added unit test to ensure they are working

Additional Notes to the Reviewer

NO_CHANGELOG=TRUE

[gopalldb]

let's reset the last flushedTime on flush, so that timer also gets reset

[samikshya-db]

Makes sense, addressed ✅