[roll third_party/pigweed] pw_env_setup: Upgrade setuptools in addition to pip

On Debian venv creation uses a fairly old version of setuptools:

  /usr/bin/python3 -m venv --upgrade /tmp/venv; /tmp/venv/bin/pip list
  Package       Version
  ------------- -------
  pip           20.3.4
  pkg-resources 0.0.0
  setuptools    44.1.1

This can cause issues installing packages, e.g.
https://github.com/pypa/setuptools_scm/issues/605

Upgrade setuptools in addition to pip. This matches the builtin behavior
of venv when passing the new --upgrade-deps option, which we could
eventually use to have these packages upgraded automatically upon venv
creation.

Also log the output of the upgrade as this might be useful later.
Debugging bootstrap is quite a bit harder when all of the output is
discarded.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/58520

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 28698d0aee4c112..00ba31c51c7a90e
Roller-URL: https://ci.chromium.org/b/8837734795988614913
Cq-Cl-Tag: roller-builder:pigweed-sample-project-roller
Cq-Cl-Tag: roller-bid:8837734795988614913
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie183d847b8fce6f9a757127e0524b75fa210f93f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/sample_project/+/58620
Bot-Commit: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>
Commit-Queue: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>
diff --git a/third_party/pigweed b/third_party/pigweed
index 28698d0..00ba31c 160000
--- a/third_party/pigweed
+++ b/third_party/pigweed
@@ -1 +1 @@
-Subproject commit 28698d0aee4c112601d8b767b4160897443e8f5a
+Subproject commit 00ba31c51c7a90ebfffec954b1dc28db015bfef3