Merge CCIP V1.6 [CCIP-2946]

[asoliman92]

Porting all CCIP V1.6 code (contracts and offchain) from ccip repo to chainlink repo.

This PR is divided into 2 steps.
First step cherry-picked changes that happened to contracts and capabilities directories.
Then fixed issues in this branch, squashed fixes and merged them here.

To review this PR you need the following:

1. Checkout the branch locally
2. Checkout ccip @6bdc1dc039
3. Run the given script (make sure both chainlink and ccip repos have same parent directory and that the script is with them in the parent)

./check-diff.sh contracts/src/v0.8/ccip
expected output:

ccip repo commit: 
6bdc1dc039 (HEAD -> ccip-develop, origin/ccip-develop, origin/HEAD) Bump chain-selectors => v1.0.23 (#1395)
chainlink repo commit: 
3dd8a72e92 (HEAD -> ccip/capabilities-debug-contracts-fmt) pnpm i && snapshot && forge fmt

Source files not modified:
     174
Source files modified:   

Then
./check-diff.sh core/gethwrappers/ccip
expected ouptut:

ccip repo commit: 
6bdc1dc039 (HEAD -> ccip-develop, origin/ccip-develop, origin/HEAD) Bump chain-selectors => v1.0.23 (#1395)
chainlink repo commit: 
3dd8a72e92 (HEAD -> ccip/capabilities-debug-contracts-fmt) pnpm i && snapshot && forge fmt

Source files not modified:
      64
Source files modified: 

Script:

#!/usr/bin/env bash

# Check if the directory is passed as an argument
if [ -z "$1" ]; then
    echo "Usage: $0 <directory>"
    exit 1
fi

# Directory to check for parity
CHECK_DIR="$1"

if [[ "$OSTYPE" == "darwin"* ]]; then
    # macOS
    SUM=gmd5sum
else
    # Assume Linux
    SUM=md5sum
fi

pushd ccip/$CHECK_DIR > /dev/null
echo -e "ccip repo commit: \n$(git log --max-count=1 --oneline --decorate)"
find . -type f -exec $SUM {} \;  > ../files.md5
popd > /dev/null
mv ccip/$CHECK_DIR/../files.md5 ./chainlink/$CHECK_DIR/../files.md5
pushd ./chainlink/$CHECK_DIR > /dev/null
echo -e "chainlink repo commit: \n$(git log --max-count=1 --oneline --decorate)"

echo ""

echo "Source files not modified:"
$SUM -c ../files.md5 2>/dev/null | grep OK | wc -l
echo "Source files modified:"
$SUM -c ../files.md5 2>/dev/null | grep -v OK

For this reason both forge fmt and solidity lint are failing the CI checks. We're taking identical copy and we're not interested in formatting them for now to make it easier reviewing the branch.

Once both are good to go please review the offchain changes and any other changes.

For clarity this is how I cherry-picked the PRs:

# How we got the commits:
# In CCIP repo:
# git log --since="2024-08-01" --reverse --pretty=format:"%H" -- contracts/src/v0.8/ccip >> contracts-commits.txt
# git log --since="2024-08-03" --reverse --pretty=format:"%H" -- core/capabilities/ccip >> cap-commits.txt
# cat contracts-commits.txt cap-commits.txt > combined_commits.txt
# git log --no-walk --pretty=format:"%H %at" $(cat combined_commits.txt) --date-order > temp_commits.txt
# sort -k2,2n temp_commits.txt | awk '{print $1}' > final_commits.txt
# have both ccip and chainlink repos under same parent directory and copy final_commits.txt and this script into the parent directory
# run this script

# Define the paths to the source and target repositories
TARGET_REPO="./chainlink"

# Read the commit hashes from the file
commits=$(cat $COMMITS_FILE)

# Navigate to the target repository
cd $TARGET_REPO

# Loop through each commit and cherry-pick it
for commit in $commits
do
    git cherry-pick $commit

    # Handle conflicts automatically
    if [ $? -ne 0 ]; then
        # Conflict resolution strategy
        # If you want to keep the changes from the source repo, you can run:
        # git checkout --theirs .
        # Or to keep the changes in the target repo, you can run:
        # git checkout --ours .

        # Example for keeping the changes from the source repo:
        git checkout --theirs .
        git add .
        git cherry-pick --continue --no-edit
    fi
done

[mateusz-sekara]

Ideally this should be one commit

[cl-sonarqube-production]

Quality Gate passed

Issues
13 New issues
5 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
77.5% Coverage on New Code
4.3% Duplication on New Code

See analysis details on SonarQube