FF Expert context awareness of FlowFuse Platform state

**Parent Deliverable:** FlowFuse/product#47 — Expert as Agentic Co-pilot

### Overview

This epic tracks the effort to make the FlowFuse Expert aware of the FlowFuse Platform state and configuration, complementing issue #6502 which focuses on Node-RED instance awareness.

While #6502 enables the Expert to understand what's happening inside a Node-RED instance (installed packages, flows, nodes), this epic enables the Expert to understand the FlowFuse Platform context (teams, projects, instances, users, permissions, etc.).

### Motivation

Users interacting with FF Expert need help managing their FlowFuse Platform, not just Node-RED flows. The Expert should be able to answer questions and perform actions related to:

- Team management and collaboration
- Instance/project lifecycle and configuration
- User roles and permissions
- Deployment pipelines and snapshots
- Platform settings and billing
- Cross-instance operations

### Related Work

- **#6502**: Context awareness of Node-RED instance state (installed packages, flows, nodes)
- **#6248**: Specific story for querying team information
- **#6505**: Settings management across multiple instances
- **#6497**: Communication framework between FF Expert and NR Assistant

### Scope

This epic covers making the Expert aware of FlowFuse Platform entities and their state:

1. **Teams & Collaboration**
- Team members and roles
- Team settings and quotas
- Team activity and audit logs

2. **Projects & Instances**
- Instance metadata (name, type, version, status)
- Instance relationships (applications, pipelines)
- Instance health and metrics

3. **Users & Permissions**
- User profiles and capabilities
- Role-based access control
- Permission boundaries

4. **Platform Operations**
- Snapshots and backups
- Deployment pipelines and stages
- Device management
- Billing and usage

5. **Configuration**
- Instance types and templates
- Environment variables
- Platform-level settings

### Implementation Approach

Similar to #6502, this will require:

1. Establishing APIs/methods for the Expert to query platform state
2. Defining the information schema and access patterns
3. Implementing appropriate permission checks
4. Creating user stories for specific capabilities
5. Building the UX for platform-aware interactions

### Future Sub-Issues

Individual user stories will be created for specific capabilities as we refine the scope and prioritize features.

### Dependencies

- #6497: Communication framework (prerequisite for all context awareness work)