Fixed AIAssistant base urls in QA

[vladtar]

Overview

Explain your changes, including any issues or relevant context about why they are needed.

For reference these urls come from outputs from deploying https://github.com/CareEvolution/SecurityAndChangeControl/blob/master/src/aws/pep/qa/open-ai-proxy/terragrunt.hcl

Security

REMINDER: All file contents are public.

• [x] I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc.
  • [x] Please verify that you double checked that .storybook/preview.js does not contain your participant access key details.
  • [x] There are no temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.
• [x] These changes do not introduce any security risks, or any such risks have been properly mitigated.

Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.

Checklist

Testing

• [ ] MyDataHelps iOS app
• [ ] MyDataHelps Android app
• [x] MyDataHelps website

Documentation

• [ ] I have added relevant Storybook updates to this PR as well.
• [ ] If this feature requires a developer doc update, tag @CareEvolution/api-docs.

Consider "Squash and merge" as needed to keep the commit history reasonable on main.

Reviewers

Assign to the appropriate reviewer(s). Minimally, a second set of eyes is needed ensure no non-public information is published. Consider also including:

• Subject-matter experts
• Style/editing reviewers
• Others requested by the content owner

Summary by CodeRabbit

• New Features

  • Introduced a new isDevelopment function to check the application environment.
  • Enhanced configurability of baseUrl and codeRunnerUrl based on the development environment.

• Bug Fixes

  • Improved handling of event parameters in the ask method of MyDataHelpsAIAssistant.

• Refactor

  • Simplified the logic for determining provider IDs by importing isDevelopment from the env module.

[coderabbitai[bot]]

Walkthrough

The changes introduced in this pull request involve the addition of an isDevelopment function to determine the application's environment, which is utilized in various components to conditionally set URLs based on whether the application is in development mode. The MyDataHelpsAIAssistant class and GraphingTool function have been updated to use this new function for setting their respective URLs. Additionally, the isDevelopment function has replaced a local definition in providerIDs.ts, streamlining the logic for determining provider IDs.

Changes

File Path	Change Summary
src/helpers/AIAssistant/AIAssistant.ts	- Added import for isDevelopment. - Modified MyDataHelpsAIAssistant constructor to conditionally set baseUrl. - Updated ask method's configurable object to include participantId.
src/helpers/AIAssistant/Tools.ts	- Added import for isDevelopment. - Updated GraphingTool to conditionally set codeRunnerUrl. - Minor formatting adjustments in SaveLastGraphTool.
src/helpers/env.ts	- Introduced isDevelopment function to check if the application is in a development environment.
src/helpers/providerIDs.ts	- Removed local isDevelopment function and imported it from ./env. - Retained logic for determining provider IDs using the imported function.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant AIAssistant
    participant Tools
    participant Env

    App->>Env: Check environment
    Env-->>App: Return isDevelopment status
    App->>AIAssistant: Initialize with baseUrl
    AIAssistant->>Tools: Initialize GraphingTool with codeRunnerUrl
    Tools-->>AIAssistant: Return initialized tool
    AIAssistant-->>App: Ready to process requests

---

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` or `@coderabbitai title` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.