Fix flaky partners requests request spec

[coalest]

Doesn't resolve any issue. But it is one of the specs mentioned in this flaky specs issue.

Description

In the spec we are expecting the family_zipcodes_list to have a certain order but no order is guaranteed in the request. This changes our expectation to match current behavior (order of zip codes doesn't matter).

Example backtrace:

  2) Partners GET #show html when the partner is invited includes impact metrics
     Failure/Error: expect(assigns[:impact_metrics]).to eq(expected_impact_metrics)

       expected: {:children_served=>4, :families_served=>3, :family_zipcodes=>2, :family_zipcodes_list=>["45612-123", "45612-126"]}
            got: {:children_served=>4, :families_served=>3, :family_zipcodes=>2, :family_zipcodes_list=>["45612-126", "45612-123"]}

       (compared using ==)

       Diff:
       @@ -1,5 +1,5 @@
        :children_served => 4,
        :families_served => 3,
        :family_zipcodes => 2,
       -:family_zipcodes_list => ["45612-123", "45612-126"],
       +:family_zipcodes_list => ["45612-126", "45612-123"],

     # ./spec/requests/partners_requests_spec.rb:130:in `block (5 levels) in <top (required)>'

(found in this comment)

Type of change

• Internal (only related to tests)

How Has This Been Tested?

I wasn't able to reproduce this failure locally. But changing the order of the zipcodes in the setup didn't break the spec so this should in theory fix the issue.

[dorner]

Neat!

[github-actions]

@coalest: Your PR Fix flaky partners requests request spec is part of today's Human Essentials production release: 2024.12.22.
Thank you very much for your contribution!