Feat/productionize examples

[jhweintraub]

Motivation

To help end users implement CCIP, we need canonical code that

1. contains Chainlink’s opinion on best practices,
2. Are a “kernel” that can be used by other Chainlink teams as part of their artifact creation in other types of educational and reference material (eg workshops, masterclasses, bootcamps, hackathons, starter kits, quick start etc)
3. external CCIP users can use and be assured of reliability and security,
4. external CCIP users can rely on if they go to mainnet

Solution

The examples and reference contracts have been refactored to better reflect these principles and simplify the process of building CCIP-compliant examples.

The following contracts have been created

1. CCIPReceiver - A basic implementation of a contract capable of receiving incoming messages from CCIP. It includes various defensive security measures such as chain & sender validation, token recovery, and manual message re-execution.
2. CCIPSender - An example of what a contract which sends arbitrary messages from external users looks like and how different CCIPSend message parameters can be configured and utilized.
3. CCIPReceiverWithACK - An extension of CCIPReceiver whereby an incoming message is processed, and then a secondary message is sent back through the bridge to the sender, acknowledging that the original message was processed correctly.
4. CCIPClient - A contract which implements both the sender and receiver functionality of the other two client types.

There are also various other contracts

1. CCIPBase - An abstract parent contract which includes management functionality such as chain validation and Ownership functions.
2. PingPongDemo.sol - An updated version of the Ping Pong example currently on the developer docs, but updated to use the defensive design patterns of CCIPReceiver.

[github-actions]

Go solidity wrappers are out-of-date, regenerate them via the make wrappers-all command

[github-actions]

Go solidity wrappers are out-of-date, regenerate them via the make wrappers-all command

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[github-actions]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[github-actions]

This PR was closed because it has been stalled for 10 days with no activity.