Add warning about issue with Arbitrum cross-chain utilities (#3626)

(cherry picked from commit 6729fec74ab7f2e896a303b5c5d661062ab127c8)

contracts/crosschain/arbitrum/CrossChainEnabledArbitrumL2.sol

@@ -17,6 +17,11 @@ import "./LibArbitrumL2.sol";
  * this specialization of {CrossChainEnabled} does not include a constructor.
  *
  * _Available since v4.6._
+ *
+ * WARNING: There is currently a bug in Arbitrum that causes this contract to
+ * fail to detect cross-chain calls when deployed behind a proxy. This will be
+ * fixed when the network is upgraded to Arbitrum Nitro, currently scheduled for
+ * August 31st 2022.
  */
 abstract contract CrossChainEnabledArbitrumL2 is CrossChainEnabled {
     /**

contracts/crosschain/arbitrum/LibArbitrumL2.sol

@@ -12,6 +12,11 @@ import "../errors.sol";
  *
  * This version should only be used on L2 to process cross-chain messages
  * originating from L1. For the other side, use {LibArbitrumL1}.
+ *
+ * WARNING: There is currently a bug in Arbitrum that causes this contract to
+ * fail to detect cross-chain calls when deployed behind a proxy. This will be
+ * fixed when the network is upgraded to Arbitrum Nitro, currently scheduled for
+ * August 31st 2022.
  */
 library LibArbitrumL2 {
     /**