* create a buildspec file which contains ctest memcheck command

* append options for both regular and pedantic valgrind check above ASAN
  check

* set up valgrind options
* set up valgrind ci codebuild check

* add comments to `CMakeLists.txt` to explain pedantic valgrind check
  logic
* change variable names to be concise
* use `VALGRIND_DEFAULT` to define `VALGRIND_PEDANTIC`
* reformat the CTest memecheck command to make it more readable
* add explanations and necessary comments to `valgrind.suppressions`

* reformat `valgrind.suppressions` comments to make them more concise
* move set Valgrind variable up. The next PR will change the location of
  set MEMORYCHECK_COMMAND_OPTIONS

* paste tracking issue's link to the comment

* relocate `include(CTest)` location to above unit testing sections

* explicitly enable `BUILD_TESTING` options in `CMakeLists.txt`
* relocate `MEMORYCHECK_COMMAND_OPTIONS` to the testing sections above
  ASAN

* remove the comments above `include(CTest)`
* update the message to set `BUILD_TESTING=ON`

* refactor some comments in `CMakeLists.txt`
* change suppressions names for valgrind and delete some comments

* relocate `include(CTest)` to the end of unit tests set up

* refactor formats

* add one wildcard to suppress backtrace memory defects for ubuntu22 and
  24 platforms

* adjust valgrind suppressions
* adjust comments format

* modify valgrind suppression comments for backtrace.

* make suppression comments more precise

Co-authored-by: Lindsay Stewart <[email protected]>