feat(sv-consumer): Introduce concurrent tasks configuration

[luizstacio]

This pull request introduces several changes across multiple files to improve concurrency management, database connection pooling, and message broker setup. The most significant changes include making the number of concurrent tasks configurable, revising database pool size and connection settings, and enhancing the message broker setup process.

Concurrency Management Updates:

• services/consumer/src/cli.rs: Added a new concurrent_tasks configuration option to allow specifying the maximum number of concurrent tasks via the CLI.
• services/consumer/src/executor/block_executor.rs: Replaced the hardcoded MAX_CONCURRENT_TASKS constant with a dynamic concurrent_tasks field, enabling concurrency settings to be passed during BlockExecutor initialization. Updated task processing logic to use this new field. [1] [2] [3] [4] [5] [6]

Database Connection Pooling:

• crates/domains/src/infra/db/db_impl.rs: Reduced the default database pool size from 2000 to 110 and added a minimum connection limit of 2 for the pool. [1] [2]
• services/consumer/src/main.rs: Updated the setup_db function to dynamically set the database pool size based on the concurrent_tasks value.

Message Broker Enhancements:

• crates/message-broker/src/nats.rs: Added a new setup_with_opts method to allow configuring message broker options, such as acknowledgment wait times.
• services/consumer/src/main.rs: Integrated the setup_with_opts method to configure the message broker with a 2-minute acknowledgment wait time.

Publisher Service Improvements:

• services/publisher/src/history.rs: Increased the chunk size for block processing from 50 to 100 and added a JoinSet for managing concurrent publishing tasks, improving efficiency and logging. [1] [2]

Test Updates:

• tests/tests/services/consumer.rs: Updated the BlockExecutor initialization in tests to include the new concurrent_tasks parameter.