Investigate approach to run Graph Explorer in AWS SageMaker Studio

## Goal

Investigate and plan an approach to allow Graph Explorer to run within AWS SageMaker Studio. Determine what constraints SageMaker Studio imposes on hosted applications, how Graph Explorer would need to adapt its architecture, and what changes are required to make it a viable deployment target.

Key questions to answer:
- What are the runtime constraints of SageMaker Studio custom apps (networking, ports, base path, authentication)?
- How would the proxy server and client be packaged and deployed in SageMaker Studio?
- Does SageMaker Studio impose a base path prefix that Graph Explorer needs to handle?
- How would Graph Explorer connect to Neptune or other graph databases from within SageMaker Studio?
- What authentication/authorization model does SageMaker Studio use, and how does it interact with database credentials?
- Are there any limitations on persistent storage, environment variables, or container configuration?

## Expected Outcome

- A written recommendation documenting the viable approaches with pros and cons
- A rough estimate of effort for the recommended approach
- A tasked-out epic if the spike confirms feasibility

## Related Issues

_None_

---

> [!IMPORTANT]
> If you are interested in working on this issue, please leave a comment.

> [!TIP]
> Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.