Inconsistent address lookup results - without unit prefix / across languages [AddressComplete]

## Description

Issue flagged by Anik in QA
> Using 219 Laurier as an address, shows two options with two postal codes, when one is selected it adds a unit number to the address that wasn't showing up in the searchable address lookup dropdown

Issue flagged by Cristina in QA.
> Bilingual input: in some cases, the same address can be found with either "street" or "rue" as keywords, in other cases.

## Steps to reproduce
1. Go to fill out a form with Address Complete
2. Try "22 Eddy Street" vs. "22 Rue Eddy" in Gatineau and see results

## Screenshots or videos

https://github.com/user-attachments/assets/421f448d-1ac7-4e3c-8019-2d4e6744d1d9

## Additional context

Consider switching from the V3 installation to V4 eventually. Test if switching helps solve this?
#7709

Start with the Address Complete integration in the NextJS form flow and reproduce the two reported cases: unit prefixes appearing only after selection, and differing results for “street” versus “rue” in Gatineau. Compare the lookup responses and the current V3 installation behavior; done means equivalent searches produce consistent results without adding an undisplayed unit.

Written by the indexing model from the issue text.