Add job to run the sample and check for memory leak

[sirknightj]

Issue #, if available:
N/A

What was changed?

• GitHub actions CI. Run the master and viewer samples both with valgrind to check for memory leaks. Instead of kill with signal 9, it interrupts the process (signal 2) and also checks for graceful exit.

Why was it changed?

• Reduce the number of times I need to manually run this check. Automating this check will also give confidence to future developers that their change did not introduce a memory leak.

How was it changed?

• Script overview:
  • Disable logs by setting log level to 7 (silent).
  • Run the master and viewer samples in the background with valgrind. The valgrind output is captured into two different files, one for each.
  • After 30 seconds, interrupt the viewer (disconnect)
  • After 30 more seconds, interrupt the master.
  • Wait for processes to exit & capture their exit status.
  • After 10 seconds, kill the master and viewer processes. Killing the processes will make them exit with non-zero exit status.
  • Check if both exited with status 0 (whether they exit gracefully on their own after interrupt).
  • Check the valgrind output files and verify that no memory leaks are detected.

What testing was done for the changes?

• Run it on the GitHub actions runner. Take a look at the image:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[sirknightj]

Output when I added a memory leak for verification: