feat: update HARVEY with SPHERE integration

[pgmarc]

Features

• Add SPHERE iPricings to pricing context directly from HARVEY
• Basic pricing filter by name
• Open SPHERE iPricings or URL A-MINT processed iPricing to further edit them in the editor
• Mirror as close as posible Pricing-Inteligence frontend

URL A-MINT frontend notification workflow

1. Frontend app connects to Server-Sent events /events endpoint
2. When user asks a question to HARVEY with URLs, their url are associated with its uuid in a in-memory db (pricing_context_db)
3. HARVEY calls iPricing tools many time as needed
4. When iPricing tool is done HARVEY stores the iPricing yaml in the static directory /harvey-api/static. The url of the pricing will have the following pattern https://sphere.score.us.es/harvey-api/static/{pricing-context-item-UUID}.yaml. Lastly, HARVEY notifies the frontend that the processing is done with the following SSE payload:

event: url-transform
data: { "id": "{pricing-context-item-UUID}", "pricing_url": "https://example.org/pricing", "yaml_content": "saasName: Testing..."} 

5. Frontend enables Open in editor button to see the iPricing in the editor

I am worried about two things:

• Whether Server-Sent events (SSE) will work in prod correctly. Sure it does on localhost.
• And If iPricings will be correctly hosted in HARVEY and no issues arise with certificates

Further changes MAY need to be done in order to work properly in production.

[javiercavlop]

From my perspective, the code looks fine. We’ll validate it during deployment, and if anything comes up, we’ll reach out.

[Alex-GF]

The frontend seems to be fine. We will check the integration on production.

P.S.: I have added some necessary configuration to production NGINX to support SSE