Send balance when contract doesn't exist (paritytech#5664)

Fixes paritytech#5577 

I decided to bubble up the error from where we actually try to load the
contract info. This helps to make sure that we don't miss some entry
point by accident. The draw back is that we have to live with some
additional `.expect`.

@pgherveou With this logic the proxy and its runtime part should be
completely unaware whether something is a contract call or a balance
transfer. They should just route everything into pallet_revive.

---------

Co-authored-by: Cyrill Leutwiler <cyrill@parity.io>

prdoc/pr_5664.prdoc

@@ -0,0 +1,11 @@
+title: Calling an address without associated code is a balance transfer
+
+doc:
+  - audience: Runtime Dev
+    description: |
+     This makes pallet_revive behave like EVM where a balance transfer
+     is just a call to a plain wallet.
+
+crates:
+  - name: pallet-revive
+    bump: patch

substrate/frame/revive/fixtures/contracts/call_return_code.rs

@@ -34,6 +34,7 @@ pub extern "C" fn call() {
 	input!(
 		100,
 		callee_addr: &[u8; 20],
+		value: &[u8; 32],
 		input: [u8],
 	);
 
@@ -44,7 +45,7 @@ pub extern "C" fn call() {
 		0u64,                // How much ref_time to devote for the execution. 0 = all.
 		0u64,                // How much proof_size to devote for the execution. 0 = all.
 		None,                // No deposit limit.
-		&u256_bytes(100u64), // Value transferred to the contract.
+		value, 				 // Value transferred to the contract.
 		input,
 		None,
 	) {