Deprecate business rules validation pages

Author: mrtnzlml

docs/learn/business-rules-validation/configuration-examples.md renamed to docs/learn/deprecated/business-rules-validation/configuration-examples.md

@@ -2,8 +2,13 @@
 sidebar_position: 1
 title: 'Business Rules Validation: Configuration examples'
 sidebar_label: 'Configuration examples'
+slug: '/learn/business-rules-validations/configuration-examples'
 ---
 
+import Deprecated from '../../\_deprecated.md';
+
+<Deprecated />
+
 # Configuration examples
 
 Here you can find examples of the most common real-world use cases for Business Rules Validation. Simply copy-paste them into extension settings and adjust as needed.

docs/learn/business-rules-validation/expression-engine.md renamed to docs/learn/deprecated/business-rules-validation/expression-engine.md

@@ -3,8 +3,13 @@ sidebar_position: 2
 title: 'Business Rules Validation: Expression Engine'
 sidebar_label: 'Expression Engine'
 toc_max_heading_level: 4
+slug: '/learn/business-rules-validations/expression-engine'
 ---
 
+import Deprecated from '../../\_deprecated.md';
+
+<Deprecated />
+
 # Expression Engine
 
 Rossum Expression Engine is responsible for validating expressions, producing either a true or false result. Its syntax closely resembles that of Python and allows for utilizing data from annotated documents. The engine assesses conditions and expressions using document data. Currently, it is employed for the Business Rules Validation extension, but there are plans to extend its usage to other extensions in the future. Engine operates at both the header field and line item levels, offering the flexibility to combine them within a single expression.

docs/learn/business-rules-validation/index.md renamed to docs/learn/deprecated/business-rules-validation/index.md

@@ -1,8 +1,13 @@
 ---
 title: 'Business Rules Validation'
 sidebar_position: 1
+slug: '/learn/business-rules-validations'
 ---
 
+import Deprecated from '../../\_deprecated.md';
+
+<Deprecated />
+
 Business Rules Validation allows users to perform validations of the extracted and calculated data. It typically runs at the end of the extension chain and the main purpose of it is to prevent confirmations (or block automation) of invalid documents.
 
 <!-- TODO: create a page (guide) describing how does chaining of extensions work! -->