Move Operations/ files to Infrastructure/ (#494)

Move 6 files from Operations/ to Infrastructure/, including
renaming Development-vs-Production.md to
Application-Development-vs-Production.md. Merge Operations
section into Infrastructure in Home.md. Remove Operations
namespace from build scripts. Update .markdownlint-cli2.jsonc
exclusion path.

Author: mensfeld

.markdownlint-cli2.jsonc

@@ -6,7 +6,7 @@
     "!Librdkafka/Statistics.md",
     "!Librdkafka/Configuration.md",
     "!Development/Karafka-Integration-Tests-Catalog.md",
-    "!Operations/Instrumentation-Events.md",
+    "!Infrastructure/Instrumentation-Events.md",
     "!WaterDrop/Instrumentation-Events.md",
     "!Changelog/*.md",
     "!Pro/License-Comm.md",

Advanced/Assignments-Tracking.md

@@ -32,6 +32,6 @@ end
 
 ## See Also
 
-- [Monitoring and Logging](Operations-Monitoring-and-Logging) - Track consumer assignments and partition distribution
+- [Monitoring and Logging](Infrastructure-Monitoring-and-Logging) - Track consumer assignments and partition distribution
 - [Web UI Features](Web-UI-Features) - Visualize partition assignments in the Web UI
 - [Concurrency and Multithreading](Concurrency-and-Multithreading) - Understanding thread safety with partition assignments

Advanced/Auto-reload-of-code-changes-in-development.md

@@ -27,5 +27,5 @@ Keep in mind, though, that there are a couple of limitations to it:
 
 ## See Also
 
-- [Development vs Production](Operations-Development-vs-Production) - Best practices for different environments
+- [Development vs Production](Infrastructure-Application-Development-vs-Production) - Best practices for different environments
 - [Getting Started](Basics-Getting-Started) - Initial setup and configuration basics

Advanced/Broker-Failures-and-Fault-Tolerance.md

@@ -446,5 +446,5 @@ Connection refused errors during broker maintenance indicate the system is worki
 - [Error Handling and Back Off Policy](Consumer-Groups-Error-Handling-and-Back-Off-Policy) - Configure retry strategies and backoff policies for consumer errors
 - [Dead Letter Queue](Dead-Letter-Queue) - Handle persistent failures by routing problematic messages to DLQ
 - [Enhanced Dead Letter Queue](Pro-Enhanced-Dead-Letter-Queue) - Advanced DLQ features for complex failure scenarios
-- [Monitoring and Logging](Operations-Monitoring-and-Logging) - Track broker connection health and system performance
+- [Monitoring and Logging](Infrastructure-Monitoring-and-Logging) - Track broker connection health and system performance
 - [Admin API](Infrastructure-Admin-API) - Programmatically inspect and manage Kafka cluster configuration

Advanced/CLI.md

@@ -114,5 +114,5 @@ Routing Patterns managament via the CLI has its own section. You can read about
 ## See Also
 
 - [Getting Started](Basics-Getting-Started) - Initial setup and basic CLI usage
-- [Deployment](Operations-Deployment) - Using CLI commands in production environments
+- [Deployment](Infrastructure-Deployment) - Using CLI commands in production environments
 - [Env Variables](Env-Variables) - Environment variables affecting CLI behavior

Advanced/Concurrency-and-Multithreading.md

@@ -150,7 +150,7 @@ There are a few ways to measure the saturation in Karafka:
 
 - You can look at the `Enqueued` value in the [Web-UI](Web-UI-Getting-Started). This value indicates the total number of jobs waiting in the internal queues of all the Karafka processes. The high value there indicates increased saturation.
 - You can log the `messages.metadata.processing_lag` value, which describes how long a batch had to wait before it was picked up by one of the workers.
-- If you are using our [Datadog](Operations-Monitoring-and-Logging#datadog-and-statsd-integration) integration, it contains the `processing_lag` metrics.
+- If you are using our [Datadog](Infrastructure-Monitoring-and-Logging#datadog-and-statsd-integration) integration, it contains the `processing_lag` metrics.
 
 Job saturation in Karafka isn't inherently critical, but it may lead to increased consumption lag, resulting in potential delays in processing tasks. This is because when the system is overloaded with jobs, it takes longer to consume and process new incoming data. Moreover, heavily saturated processes can create an additional issue; they may exceed the max.poll.interval.ms configuration parameter. This parameter sets the maximum delay allowed before the Kafka broker considers the consumer unresponsive and reassigns its partitions. In such a scenario, maintaining an optimal balance in job saturation becomes crucial for ensuring efficient message processing.
 

Advanced/Debugging.md

@@ -596,7 +596,7 @@ Don't hesitate to get in touch if you still need clarification after following t
 ## See Also
 
 - [Problems and Troubleshooting](Problems-and-Troubleshooting) - Common issues and their solutions for Karafka applications
-- [Monitoring and Logging](Operations-Monitoring-and-Logging) - Configure comprehensive logging and monitoring for debugging
+- [Monitoring and Logging](Infrastructure-Monitoring-and-Logging) - Configure comprehensive logging and monitoring for debugging
 - [Error Handling and Back Off Policy](Consumer-Groups-Error-Handling-and-Back-Off-Policy) - Understand error handling mechanisms and retry logic
 - [Support](Pro-Support) - Access priority support and direct assistance from the Karafka team
 - [FAQ](Basics-FAQ) - Frequently asked questions about Karafka functionality and troubleshooting

Advanced/Embedding.md

@@ -265,4 +265,4 @@ The listener thread priority (internal setting `internal.connection.listener_thr
 ## See Also
 
 - [CLI](CLI) - Command-line interface for running Karafka standalone
-- [Deployment](Operations-Deployment) - Strategies for deploying Karafka in various environments
+- [Deployment](Infrastructure-Deployment) - Strategies for deploying Karafka in various environments

Advanced/Env-Variables.md

@@ -32,5 +32,5 @@ Karafka's behaviour can be altered with the following environment variables:
 ## See Also
 
 - [Configuration](Basics-Configuration) - Complete configuration reference
-- [Deployment](Operations-Deployment) - Using environment variables in deployment
-- [Development vs Production](Operations-Development-vs-Production) - Environment-specific settings
+- [Deployment](Infrastructure-Deployment) - Using environment variables in deployment
+- [Development vs Production](Infrastructure-Application-Development-vs-Production) - Environment-specific settings

Advanced/Exit-codes.md

@@ -27,5 +27,5 @@ Each Karafka process defines exit statuses to indicate how the process terminate
 
 ## See Also
 
-- [Deployment](Operations-Deployment) - Handling exit codes in production deployments
-- [Signals and States](Operations-Signals-and-States) - Understanding process lifecycle and signals
+- [Deployment](Infrastructure-Deployment) - Handling exit codes in production deployments
+- [Signals and States](Infrastructure-Signals-and-States) - Understanding process lifecycle and signals