Flow deprecation and vulnerability info into search service

[xavierdecoster]

Package deprecation info needs to flow into search service.
Required for phase 2 of package deprecation PMUI and more advanced search filtering.
Required for displaying deprecation and vulnerability information in NuGet.org search results page.

general:

• https://github.com/NuGet/Engineering/issues/4501
• https://github.com/NuGet/Engineering/issues/4615
• https://github.com/NuGet/Engineering/issues/4751

v3 search endpoint:

• https://github.com/NuGet/Engineering/issues/4502
• https://github.com/NuGet/Engineering/issues/4616
• https://github.com/NuGet/Engineering/issues/4760

v2 search endpoint:

• https://github.com/NuGet/Engineering/issues/4733

NuGet.org:

• https://github.com/NuGet/Engineering/issues/4734

[scottbommarito]

Likely not needed for MVP.

[skofman1]

removing out of the Epic, since it covers only the MVP.

[nkolev92]

Once this is fixed, we'd appreciate a heads up so we can fix the NuGet.Client side experience: NuGet/Home#8719

[nkolev92]

This is a blocker for NuGet/Home#8058.

[nkolev92]

@joelverhagen @loic-sharma

Is this on any roadmap as of now?
This would really help improve the performance of PM UI browse scenarios.

[joelverhagen]

Nope, not scheduled right now. Let's talk offline with @skofman1 about when this could happen w.r.t. to our other commitments.

[skofman1]

@nkolev92, since this is needed for an e2e experience (client perf improvement) we need to align priorities & schedules between the teams. i.e., how high is NuGet/Home#8058 on the client team backlog? Right now I see it marked as P3. We can discuss further offline.

[nkolev92]

Sounds good. I think the first target would be: NuGet/Home#10865.

I've started a discussion to prioritize that issue from a client perspective.
I'll tag you in the chat for reference.

Thanks @joelverhagen @skofman1!

[JonDouglas]

Can we merge this? Or does it still need docs and rebuilt index?