[DEV-11765] Fix subaward zip bug

[sethstoudenmier]

Description:

Use the 5-digit zip code for subawards instead of the larger form zip code.

Technical Details:

There are a few small changes grouped into this PR:

• Use the sub_pop_zip5 instead of sub_pop_zip when filtering the zip code on Subawards. This is a pattern we use for both Awards and Transactions, and I was unable to see a reason why we would use the longer form zip code at this time. Optionally, we could support querying the longer form zip code (and changes were initially queued up for this), but that adds extra functionality that I don't believe was intended at this time.
• Some minor cleanup of the location filters that could use some additional refactoring in order to be more DRY, but I wanted to limit the changes in this PR as it was already touching some items outside of scope.
• When initially writing test cases I noticed an issue with the sorting on Sub-Award ID field. Sorting on Sub-Award ID was previously sorting on the Prime Award's value for display_award_id which is confusing because the Sub-Award ID is actually the subaward_number. This was corrected initially for the purpose of test cases although that has since changed. But this change was left in place as it is a small bug that improves UX on the site and API.
• Slight change to the Primary Place of Performance zip code logic that will use the sub_pop_zip5 value when the sub_pop_zip value is not 5 or 9 characters. This was causing a weird UI bug where a Subaward would appear in the filter, but the zip code wouldn't show on the page because the sub_pop_zip often has extra characters in it.

Requirements for PR Merge:

1. Unit & integration tests updated
2. API documentation updated (examples listed below)
   1. API Contracts
   2. API UI
   3. Comments
3. Data validation completed (examples listed below)
   1. Does this work well with the current frontend? Or is the frontend aware of a needed change?
   2. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
   3. Is the expected data returned with the expected format?
4. Appropriate Operations ticket(s) created
5. Jira Ticket(s)
   1. DEV-11765

Explain N/A in above checklist:

[sethstoudenmier]

While I really want to correct the formatting on this file, it would greatly inflate the changeset for the PR.