Fix sensor errors related to empty GraphQL query

[MarcAstr0]

Description

Some health sensor endpoints require making an empty request to the GraphQL endpoint. Making this request with an empty body caused errors which caused other sensors to appear without response. (e.g., returned an empty array):

error: [Booster]|BoosterGraphQLDispatcher#runGraphQLOperation: Received an empty GraphQL query

This PR fixes this error by sending a minimal GraphQL query in the request body.

Changes

• Modifies health-adapter.ts in both Azure and local providers so that isGraphQLFunctionUp method sends the following in the request body:

{
  "query": "query { __typename }",
}

[what-the-diff]

PR Summary

• Added Documentation for Sensor Fixes
  A new file has been added, named fix_sensors_2025-03-24-19-38.json. This file provides detailed documentation related to updates and problem-solving efforts around the behavior of certain sensors in our system.

• Updated Software Dependencies
  We've updated the specifications for numerous software components that our system relies on. These updates appear in a file called pnpm-lock.yaml and involve several system packages. The goal here is to keep up-to-date with advancements in these software components and benefit from any improvements made.

• TypeScript Version Upgrade
  TypeScript is a programming language we use, and we've upgraded to a newer developmental version. This could allow us to build more feature-rich and secure applications.

• Improved Data Request Handling
  We've changed how our system handles certain types of data requests (specifically, GraphQL requests) in particular system components (framework-provider-azure and framework-provider-local). The modification aims to include more detailed information in the request, which may result in better system performance and reliability.

[MarcAstr0]

/integration sha=241f3b6efb35583316e32bb23312e80fe08ac492

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[github-actions]

❌ Oh no! Integration tests have failed

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[github-actions]

❌ Oh no! Integration tests have failed

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[github-actions]

❌ Oh no! Integration tests have failed

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[github-actions]

❌ Oh no! Integration tests have failed

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[github-actions]

❌ Oh no! Integration tests have failed

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[davidverdu]

I approved it, but the integration tests should pass before merging

[github-actions]

❌ Oh no! Integration tests have failed

[MarcAstr0]

/integration sha=f331c1b4c84dce91559062c5a5444682550f0fbd

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[github-actions]

✅ Integration tests have finished successfully!