feat: Enable data separation for each MixPanel API instance

[surajbokey-cred]

Introducing Database Separation for Streamlined Event Routing

This pull request addresses the challenge of event data being directed to both Mixpanel and the proxy server due to a single database setup.

Problem:

Currently, all events are stored in a centralized database, regardless of their intended destination (Mixpanel or proxy server). This makes it impossible to control which events flow to each server.

Solution:

This pull request implements separate databases for each server, named according to their unique instanceName. This ensures events are routed to the appropriate server based on their origin.

Implementation:

• The creation process for databases and AnalyticsMessage objects has been modified to utilize the instanceName instead of a context-based key.
• This change guarantees the creation of distinct databases for each server, enabling proper event segregation.

Benefits:

• Improved Data Control: This solution allows for precise control over event routing, eliminating the unintended duplication of data across servers.
• Enhanced Efficiency: Separating data streams can potentially enhance performance and resource utilization for both Mixpanel and the proxy server.