Add Additional Configuration Information (including EAS config) to API `config` Endpoint

[johnx25bd]

Description
We need to extend our existing API endpoint to include new configuration details. The primary focus is on adding EAS configuration parameters (i.e. found here) but we should also ensure that any additional relevant config information is included. This will help streamline our deployment workflows and ensure feature consistency across different environments.

Acceptance Criteria

1. Add EAS Configuration Fields

   • Implement the ability to send/receive EAS configuration details within the endpoint.
   • Ensure compatibility with existing configurations. This includes modifying the object to include schema versions ("v0.1", currently)

2. Documentation

   • Update the API specification to reflect the new configuration fields.
   • Provide examples showing how to use the new EAS config details.

3. Testing

   • Write tests confirming that EAS config information is properly handled.
   • Verify that existing configuration remains unaffected when EAS details are absent.

Additional Details

• Investigate whether any additional security considerations are needed (e.g., masking sensitive EAS credentials in logs).
• Coordinate with the DevOps team to ensure the new EAS config aligns with deployment pipelines.

Notes

• Please provide any feedback or suggestions regarding the naming of new config fields and how we reference them in the endpoint structure.
• We may need to schedule a follow-up to confirm the final approach for environment-specific EAS configurations.

Tasks

1. Update the API model to include new EAS configuration fields.
2. Update the API endpoint request/response schema documentation.
3. Write unit and integration tests for EAS config handling.
4. Coordinate with DevOps to confirm proper handling and deployment of the new config details.

Label: Enhancement
Estimated Time: Medium

Feel free to add or modify any details if something is missing or needs further clarification.