Kill MessageType::SHUTDOWN related logic in pg agent

[rohan-varma]

#30330 got rid of the need to send a MessageType::SHUTDOWN message, so we can now remove the logic/utils for this type of message.

I think we can also delete the enum entry in the enum MessageType, but we may want to keep it in case the logic in #30710 is ever moved to C++.

Test plan: All existing unit tests pass

[xush6528]

make sense to me. This message type is not used now.

[facebook-github-bot]

@rohan-varma has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[facebook-github-bot]

@rohan-varma has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[facebook-github-bot]

@rohan-varma has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[pritamdamania87]

Let's kill the enum as well (and bring it back later if needed). Otherwise accidentally using that enum might cause some unintended behavior since the message type is not handled.

[facebook-github-bot]

@rohan-varma has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[kostmo]

💊 CircleCI build failures summary and remediations

As of commit f43297b:

• 7/7 broken upstream at merge base 1e116a5 (see grid view)

  You may want to rebase on the viable/strict branch (expand for instructions)

  If your commit is newer than viable/strict, you can try basing on an older, stable commit:

  git fetch viable/strict
  git rebase --onto viable/strict $(git merge-base origin/master HEAD)
  

  If your commit is older than viable/strict:

  git fetch viable/strict
  git rebase viable/strict
  

  Check out the recency history of this "viable master" tracking branch.

• 0/7 failures introduced in this PR

Detailed failure analysis

One may explore the probable reasons each build failed interactively on the Dr. CI website.

🚧 7 upstream failures recognized by patterns:

These builds matched patterns, but were probably caused by upstream breakages:

• pytorch_linux_xenial_py3_6_gcc5_4_test
• pytorch_macos_10_13_py3_test
• pytorch_linux_xenial_py3_clang5_asan_test
• pytorch_linux_xenial_cuda9_cudnn7_py3_nogpu_test
• pytorch_linux_xenial_cuda9_cudnn7_py3_test
• pytorch_linux_xenial_cuda9_cudnn7_py3_NO_AVX2_test
• pytorch_linux_xenial_cuda9_cudnn7_py3_NO_AVX_NO_AVX2_test

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker.

This comment has been revised 8 times.

[facebook-github-bot]

@rohan-varma has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[rohan-varma]

Failures and lint are unrelated, landing.

[facebook-github-bot]

@rohan-varma merged this pull request in 348d421.