[hma] Match Lookup API that provides more metadata

[Dcallies]

Today's Lookup APIs

https://github.com/haianhng31/ThreatExchange/blob/8d10599cda78afa49f763c08ca556db94f4ae332/hasher-matcher-actioner/src/OpenMediaMatch/blueprints/matching.py

Ideal Usecase - Reddit Request

@aokolish representing request:

Input:

1. Required
   1. Signal type
      1 .hash
2. Optional
   1. Resolve 3P record json

Output:
List of match objects:

   Bank: [
       bank_content_id: {
          distance
          // Example
          3P_exchange_type:  exchange_type: NCMEC
          3P_Records: {3p_id: NCMEC_ID        
              exchange_data: {  // Specific to exchange type
                  member_entries: {
                     member_id: [tags]
              }
          } 
       }
   ]

Notes:

• Do not return disabled hashes or banks

[aokolish]

@Dcallies do you have strong feelings about the URL of this API? I was thinking to implement it as a new route since it's quite different and I don't want to break anyone else's API client.

The current route is - /m/lookup. I was thinking about /m/lookup_advanced or /m/lookup_v2; thinking of a good name is hard.

[ThisIsMissEm]

@Dcallies this is something else that we can tackle under that v2 API design that we've discussed.

[Dcallies]

This issue was mentioned as a being a priority to an adopting platform in the 7/16/2025 HMA development meeting.

[julietshen]

@sreeprasad is working on this via #1931. Part of a related issue #1925