Implement get_script command for improved script retrieval in MCP

- Introduced a new `get_script` command to allow agents to read script source code directly from Roblox Studio, enhancing conflict resolution during sync operations.
- Updated the MCP stream handling to support the new command, including error handling for missing or invalid parameters.
- Enhanced the App component to manage the `get_script` command and its response, ensuring proper integration with the existing MCP functionality.
- Updated the TODO list to reflect the addition of the `get_script` command and its associated documentation requirements.

These changes aim to improve the overall functionality and user experience of the MCP integration, particularly in script management.

TODO.txt

@@ -341,11 +341,10 @@ can we allow the terminal to stay so i can like run some git commands myself wit
   - we should steal this system fully: D:\UserGenerated\studio-rust-mcp-server\plugin\Utils\Paths.luau
   - in the sync feedback it gives, we should include Paths.GetRelativePath so the agent is able to find it via the read_script ALONGSIDE the current info we can give so it can also find it on the Atlas filesystem
   - investigate this further, because i just want to give the agent the best possible way to query roblox instances, and also atlas instances on the filesystem. if using this Paths module is an overstep and we can accomplish it with a fully atlas-based approach, that's fine - aslong as it works CONSISTENTLY and is simple.
-* get_script_history PATH
- - 
 * port all of the basic MCP endpoints offered via https://github.com/Roblox/studio-rust-mcp-server
  - integrate them into how we've done our mcp in atlas
  - make sure to handle the placeid filtering like we already do when establishing the connection
+ - we've done some actual fixes over at D:\UserGenerated\studio-rust-mcp-server on these, we should probably pull those fixed versions! we don't need that whole studio selection system from over there, though.
 * syncback
  - invokes plugin based syncback
  - ensure this doesn't interrupt the connection of the mcp, since i think we shutdown the api? we should just not shutdown the api or something
@@ -353,6 +352,8 @@ can we allow the terminal to stay so i can like run some git commands myself wit
  - also add logging for commands (including the json) it runs and the resulting json. try to keep this on one line please, json compact.
 * ensure all mcp route documentation is well formed and gives the agent knowledge on how to use this system to the fullest.
  - I did .md based docs over with my D:\UserGenerated\studio-rust-mcp-server codebase, we should probably switch to this as it's cleaner
+ - Instruct on good sync flow, with get_script merging.
+  - If user requests get_script and we havn't sync'd yet, just do a dryrun sync to get the instance id map going.
 
 [sync]
 right now sync is running REALLY slow