[Feature Request]: Add Export/Import Functionality for Agents

[ColtonShawProctor]

What features would you like to see added?
Add the ability to export and import agent configurations, similar to the functionality that existed for the deprecated Presets feature.
More details
Use Case:
We run multiple LibreChat instances with specific agents configured for different purposes. We need to be able to quickly export these agents with their configurations and import them to other LibreChat instances. Currently, we have to manually recreate each agent, which is time-consuming and error-prone.
Current Situation:

The deprecated Presets feature had export/import functionality via JSON files
The new Agents feature (which replaced Presets) does not have this capability
Users cannot easily transfer agent configurations between LibreChat instances
Teams managing multiple instances must manually recreate agents for each deployment

Specific Needs:

Deploying the same agents across development, staging, and production environments
Sharing proven agent configurations between team instances
Backing up complex agent configurations
Ensuring consistency of agents across multiple deployments

Proposed Solution Options:
We're open to whatever approach works best with LibreChat's architecture. Some possibilities:

Full Export/Import: Export complete agent configuration including all settings, though we understand file attachments and user-specific permissions might complicate this
Agent Templates: Export a simplified "template" containing just the agent's core configuration (name, instructions, model settings, capabilities, enabled tools) without user-specific data or file attachments
Configuration-as-Code Enhancement: Improve the existing librechat.yaml modelSpecs to support more agent features, making it a more complete solution for agent deployment

Technical Considerations:
We recognize there are complexities to consider:

File attachments in agent context might need special handling or be excluded
ACL permissions would likely need to be reset on import
Tool configurations (API keys, MCP servers) would need to be configured separately on the target instance

Questions for the Team:

What approach would align best with LibreChat's current architecture?
Are there existing patterns from the conversation import/export feature that could be reused?
Would a phased approach work better (e.g., starting with basic config export, adding file handling later)?

Current Workarounds (all have significant limitations):

Manually recreating agents in each instance (time-consuming, error-prone)
Configuring agents via librechat.yaml using modelSpecs (requires server access, restart, and doesn't capture all agent features)
Using a shared MongoDB database (not practical for separate environments)

Additional Context:
As LibreChat adoption grows in enterprise environments, the ability to maintain consistent agent configurations across instances becomes critical for operational efficiency and governance.
Happy to provide more details about our use case or help test any implementation.