feat: add goroutine watcher

[jake-shin0]

• queryer was managed as a separate dir and its implementation was divided. (cgroup & runtime)
• Queryer interface method to public.
• As I was dividing queryer, I also wanted to manage profiler in dir, but I did not consider this part.
• Since both monitor and profile are managed through the profile singleton object in pprof lib, I considered implementing it by injecting and managing a common singleton object in queryer and profiler, but did not do so.
  • The singleton object inside the pprof lib is managed as a map, making its usability convenient, but the public function it returns is a list, making its usability a bit ambiguous.
  • if creating an internal singleton object, it must be taken care of concurrency issues.
  • It is not a frequently called object, and its call frequency is determined by ticker, so pprof lib is used in both queryer and profiler.