Update compat docs for CI and rebuild (#2481)

Author: skudasov

book/src/framework/compat.md

@@ -1,14 +1,34 @@
 # Compatibility Testing
 
-## Prerequisites
+## Integrating Compatibility CI
+
+To create CL node compatibility CI in your reporisoty follow these steps:
+
+1. Setup role to pull CL and JD [images](https://github.com/smartcontractkit/infra/tree/master/accounts/production/global/aws/iam/roles/gha-smartcontractkit).
+Add it to your secrets:
+```bash
+gh secret set MY_SECRET
+# enter your secret, it should be something like:
+# arn:aws:iam::<prod_registry>:role/gha-smartcontractkit-public-ecr <- name for your role
+```
+
+2. Copy this [pipeline](https://github.com/smartcontractkit/chainlink/blob/sot-upgrade-workflow/.github/workflows/devenv-compat.yml) to your repository
+
+3. Add nightly pipeline for your product, see `df1-compat` [example](https://github.com/smartcontractkit/chainlink/blob/sot-upgrade-workflow/.github/workflows/devenv-nightly-compat.yml#L42)
+
+## Usage
+
+### Prerequisites
 
 Authorize in our SDLC ECR registry first. Get the creds and run
 
 ```bash
 aws ecr get-login-password --region us-west-2 | docker login --username AWS --password-stdin <sdlc_ecr_registry>
 ```
 
-## Testing Upgrade Sequence
+If you don't have `ctf` CLI, download it [here](https://smartcontractkit.github.io/chainlink-testing-framework/framework/getting_started.html)
+
+### Testing Upgrade Sequence Locally
 
 We have a simple tool to check compatibility for CL node clusters. The example command will filter and sort the available tags, rollback and install the oldest version, and then begin performing automatic upgrades to verify that each subsequent version remains compatible with the previous one.
 
@@ -44,7 +64,7 @@ ctf compat backward \
 
 In case you have multiple DONs in your product and names of nodes are different please use `--node-name-template custom-cl-node-%d` option
 
-## Modelling Node Operators Cluster (WIP)
+### Modelling Node Operators Cluster (WIP)
 
 It is possible to fetch versions node operators are currently running and model DON upgrade sequence locally. When `product` is specified, `compat` will fetch the current versions from the RANE SOT data source and model the upgrade sequence for versions found on real DONs up to the latest one, each node one at a time.