Fix multiple dashboard-related routes using the API key's project instead of a specified project

# Overview

Currently, there are several routes (e.g. analytics) using only the project ID associated with the API key. This makes it problematic for e.g. the dashboard, where the API key would always be tied to project 0. If someone tried to create an analytics config on a new project, it would actually just modify it for project 0.

# Requirements

- [ ] Juno should be able to take in a project ID for these routes
- [ ] **Juno still needs to check whether the API key would have access to this project. ADMIN should only have access to the projects assigned to the API key; SUPERADMIN can access any project.**
- [ ] Update the juno-sdk and juno-dashboard as necessary to demonstrate the new functionality.