Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
• I've read the Contribution Guidelines
• I've updated the documentation if necessary.
• I've added or updated relevant unit tests.

Motivation and Context

Resolves #29878

Description

While troubleshooting the linked issue #29878 I found that on App Store Connect there are builds and also build uploads. A basic difference is that build uploads show builds that are currently uploaded (which an actual "normal" build isn't showing)

I tested everything with my exactly use case. Using the build uploads api from App Store Connect resulted into the behavior I expected. Everything else should work as before (except that build uploads be taken into account)

Note: The latest_testflight_build_number action uses the app_store_build_number action under the hood, which is why it is also affected by my change. However, no special adjustments were necessary in this regard, as the action could almost be considered an alias, as it appears to me.

Note 2: I'm still quite new to fastlane and especially to ruby.

Testing Steps

Test with the following action call / parameters:

platform :ios do
  lane :build_number do
    api_key = app_store_connect_api_key(
      key_id: ENV['APPLE_KEY_ID'],
      issuer_id: ENV['APPLE_ISSUER_ID'],
      key_content: ENV['APPLE_KEY_CONTENT'],
      is_key_content_base64: true,
      duration: 1200,
      in_house: false
    )
    app_store_build_number(
      api_key: api_key,
      app_identifier: ENV['BUNDLE_IDENTIFIER'],
      live: false
    )
  end
end

While a build is uploading the app_store_build_number action should return the currently uploading build number. Before my change an even older one (from the last completed processed build) was returned.