Fix nodepool dependency issues

There are two nodepool dependency issues affecting our ability to run
tests and build container images. One related to IBM cloud package
dependency resolution and the other a yappi compilation problem on
aarch64.

Recent updates to IBM cloud dependencies have triggered pip dependency
resolution to go into full scan mode. Ultimately, this appears to end up
scanning old packages that don't have the required requirements.txt
content and pip dep resolution breaks due to being unable to find
transitive dependencies. (This is likely a broken package that should be
pulled from pypi). Work around this by setting our lower bounds on these
packages to the versions available on April 28, 2025.

Additionally, yappi only publishes wheels for x86_64 so when we install
yappi in our debian aarch64 containers we must compile it to produce an
installable wheel. This fails with:

  gcc: internal compiler error: Segmentation fault signal terminated program cc1

I suspect that this stopped working when Debian Bookworm 12.11 was
released on May 17, 2025 which would've updated many system level
packageson Bookworm. To workaround this for now we simply stop
installing yappi on aarch64. This will reduce our ability to debug
nodepool on that platform, but nodepool in zuul should eventually
mitigate the problems with this.

Change-Id: I2b753dbe793661ba6f29ce04961062ae97bd66b6

requirements.txt

@@ -26,6 +26,6 @@ google-api-python-client
 # botocore 1.23.0 (via boto3 1.20.0) requires urllib 1.26.0 or newer:
 #  https://github.com/boto/botocore/issues/2562
 urllib3>=1.26.0
-ibm-vpc
-ibm-platform-services
-ibm-cos-sdk>=2.11.0
+ibm-vpc>=0.28.0
+ibm-platform-services>=0.64.0
+ibm-cos-sdk>=2.14.0

setup.cfg

@@ -32,7 +32,7 @@ warning-is-error = 1
 
 [extras]
 nodepool_base =
-    yappi
+    yappi;platform_machine!='aarch64'
     objgraph
     python-logstash-async