Currently, the podspecs repo command fails when run on an M1 machine:

• macOS: ld: warning: [...]/Pods/FlutterMacOS/FlutterMacOS.framework/FlutterMacOS, building for macOS-arm64 but attempting to link with file built for macOS-x86_64. @cbracken Shouldn't that framework be universal on master?
• iOS dependencies. E.g.: ld: building for iOS Simulator, but linking in object file built for iOS, file '[...]/Pods/GoogleMaps/Maps/Frameworks/GoogleMaps.framework/GoogleMaps' for architecture arm64. @jmagman Is this something we can adjust about how pod does its validation build, the way we have for the Runner?

Currently the full list of failures is:

The following packages had errors:
  file_selector_macos:
    file_selector_macos.podspec
  google_maps_flutter/google_maps_flutter:
    google_maps_flutter.podspec
  google_sign_in_ios:
    google_sign_in_ios.podspec
  path_provider_macos:
    path_provider_macos.podspec
  shared_preferences_macos:
    shared_preferences_macos.podspec
  url_launcher_macos:
    url_launcher_macos.podspec

This currently prevents moving this task to M1 machines, but it's also problematic for local development as more people move to M1 machines.

/cc @jmagman @cbracken