🚀 Add OpenAI integration and optimize video creation process

This commit introduces OpenAI integration and improves the video creation process. Here's a breakdown of the changes:

1. Add 'ruby-openai' gem to Gemfile
2. Configure OpenAI in boot.rb
3. Optimize Pace.js usage in app.js and _head.erb
4. Refine narration in gathering creation test
5. Streamline video generation process in test_config.rb

🚨 Add error logging for MaxMind download failures

💰 Increase contribution requested per event from £20 to £25

This change updates the standard contribution amount requested for each event from £20 to £25. This adjustment likely reflects a need to cover increasing costs or to better support the organization's activities.

🐛 Fix waitlist addition check in events controller

This commit improves the reliability of the waitlist addition process by changing the condition that checks if a user was successfully added to the waitlist. Instead of checking if the newly created waitship is persisted, we now verify if the waitship exists in the database by querying for it directly. This change ensures a more accurate confirmation of the waitlist addition.

🐛 Increase sleep duration in Squarespace account creation task

This commit increases the sleep duration from 10 to 30 seconds in the Squarespace account creation task. This change is made to allow more time for the account creation process to complete, reducing the likelihood of false negatives when checking for the newly created account.

🐛 Fix access to deleted events and related data

This commit addresses an issue where deleted events and their associated data (orders, tickets, donations) were not accessible in certain views. The changes ensure that administrators can view and manage this data even for deleted events, improving data accessibility and management.

♻️ Refactor StripeCharge balance and fee calculation methods

Rename methods for clarity and consistency: - calculate_balance to balance_from_transactions - calculate_fees to fees_from_transactions

Update task to use new method names when setting balance and fees.

This change improves code readability and better reflects the methods' functionality, deriving values from transactions rather than calculation.

⚡️ Optimize event accounting methods with memoization

This commit improves performance by implementing memoization for several methods in the EventAccounting module. The changes include:

1. Refactoring instance variable creation in profit_share_roles method
2. Adding memoization to credit_applied, credit_on_behalf_of_organisation, credit_on_behalf_of_revenue_sharer, fixed_discounts methods
3. Implementing memoization for discounted_ticket_revenue
4. Optimizing donation_revenue, organisation_discounted_ticket_revenue, and revenue_sharer_discounted_ticket_revenue with conditional memoization

These optimizations will reduce unnecessary recalculations and improve overall performance of the event accounting system.

⚡️ Implement memoization for expensive calculations in EventAccounting and StripeCharge

This commit improves performance by implementing memoization for expensive calculations in the EventAccounting module and StripeCharge model. The changes reduce redundant computations by caching results of method calls, which can significantly speed up subsequent accesses to the same data.

✨ Add partials for event stats row components

This commit introduces a series of partials for each component of the event stats row. This refactoring improves code organization, readability, and maintainability by breaking down the large _event_stats_row.erb file into smaller, more manageable pieces.

The changes include:

1. Creating separate partial files for each component of the event stats row.
2. Updating the main _event_stats_row.erb file to use these new partials.
3. Passing necessary local variables to each partial.

This modular approach allows for easier updates and modifications to individual components of the event stats row in the future.

🔥 Remove admin accounts from refund failure notifications

This commit removes the inclusion of admin accounts in the refund failure notification process. Now, only event facilitators will receive these notifications, streamlining the communication process and reducing unnecessary notifications to admin accounts.

✨ Add notification system for failed refunds

This commit introduces a new feature to notify administrators and event facilitators when a refund fails. It includes:

1. New email templates for failed order and ticket refunds
2. Implementation of notification methods for both Order and Ticket models
3. Integration of these notifications into the refund process

🔥 Remove Hotjar and Simple Analytics tracking scripts

This commit removes the inclusion of Hotjar and Simple Analytics tracking scripts from the head partial. This change is likely made to reduce the number of third-party scripts loaded on the page, which can improve page load times and enhance user privacy.

🐛 Add error logging for timezone setting failure

🐛 Fix potential nil error in StripeWebhooks module

🚀 Add convenience method for finding Gathering by slug

♻️ Refactor search_events method for improved performance

The search_events method has been refactored to use a more efficient MongoDB query. This change replaces multiple separate queries with a single $or query, which should result in better performance and cleaner code.

🐛 Fix search_events method to work with Mongoid::Paranoia

The search_events method was refactored to address an issue with Mongoid::Paranoia breaking the .or query. The new implementation uses .and and .pluck to achieve the same result, ensuring compatibility with Mongoid::Paranoia and maintaining the search functionality across name, description, and location fields.

✨ Enhance account creation process with multiple entity support

This commit expands the account creation functionality to support various entities such as organizations, activities, local groups, and events. It allows for more flexible user onboarding and association with different parts of the system.

💬 Update text for price selection instruction in ticket purchase view

The commit updates the instruction text for selecting a price in the ticket purchase view. This change aims to provide clearer guidance to users when interacting with the price selection feature, specifically for ticket types with a price range.

🔥 Remove unused AI and machine learning gems from Gemfile