Allow NWW, NWS, and NWP to be used as the "office" string within CDA

As it stands, in order to interact with NWW data on CDA, the office string "NWDP" needs to be used as the office string. I noticed in the catalog endpoint, if the primary office is set to NWDP, I am able to set the bounding office to NWW and get a list of only the gauges that are utilized by NWW (https://cwms-data.usace.army.mil/cwms-data/catalog/TIMESERIES?office=NWDP&bounding-office-like=NWW).

I was wondering if there would be a way to make it so putting NWW in the office field will directly filter NWW bounding office data from NWDP as both internal and external users might not know to search under NWDP? The example I looked at is that SPA is under the SPD division but you can access SPA data specifically without having to include a “bounding-office-like” field

Start by examining the catalog TIMESERIES endpoint behavior for office and bounding-office-like, using the NWW/NWDP example URL and the SPA/SPD comparison in the issue. Determine how NWW, NWS, and NWP should resolve when supplied as office values, then verify that each returns only its corresponding bounding-office data without requiring an additional filter.