Add support for mapping data to local AA bot runs via co-pilot

[twschiller]

Context

• In https://github.com/pixiebrix/pixiebrix-extension/issues/7104 we added support for passing data to processes in the co-pilot

Implementation Sketch

• Introduce a separate host data tracking for botIds
• If botId is provided from the copilot, respond with the bot data

Discussion

• Do we want to use the same brick? Or introduce a different brick for botId? It's likely better to use the same brick to avoid brick proliferation
• Could introduce by keeping a single id field and introducing a field to indicate what kind of id it is. Or could introduce a separate botId field with the requirement that at least one is provided
• If introducing a new field, nice to have is to write a custom options view for the brick