AUTH-API / AUTH-WEB / NAMEX / LEAR - Freeze and Unfreeze - Change dashboard into two calls into LEAR and NAMEX

[MatthewCai2002]

• We'll have to build two new search routes that need to be called - in Namex and LEAR.
• The frontend will also require a rewiring.

[JohnamLane]

Hey team! Please add your planning poker estimate with Zenhub @seeker25 @kialj876 @MatthewCai2002 @Jxio

[seeker25]

1. Create new search route in NAMEX
2. Create new search route in LEAR
3. Light performance testing - Optimized so it only returns the columns necessary with no performance implications on LEAR/ NAMEX
4. Rewire the frontend
5. Clean up - Minor changes to affiliations (so they include the business_identifier) / Remove Entity table

[seeker25]

@JohnamLane this needs to be re-estimated a tad, might be a bit higher. Especially considering members of our team have never ran NAMEX or LEAR before.

[Kaineatthelab]

@JohnamLane is this a rearchitecture of the calls, will it move us away from the previous work that was done on the dashboard? Just checking @thorwolpert has vetted this or there was a RFC or maybe it didn't need one?

[seeker25]

@Kaineatthelab

Thor Wolpert has vetted this. We've had multiple discussions with him regarding this change.

The business pushed back regarding us changing the business dashboard page into two different tabs (one for names and one for businesses), so we're going to do the filtering on the client side and merge the data from Namex/ LEAR.

We still need two calls into Namex/Lear to fetch all of the data in one shot.