feat: prepare for 1.20.0 release

[bowenwang1996]

Stabilize multiple protocol features

Test plan

Nayduck http://nayduck.eastus.cloudapp.azure.com:3000/#/run/1711

[frol]

Are these features documented?

@khorolets @telezhnaya please, keep in mind the AllowCreateAccountOnDelete feature.

nearcore/runtime/runtime/src/actions.rs

Lines 519 to 559 in 5a81fa0

	if checked_feature!(
	"protocol_feature_allow_create_account_on_delete",
	AllowCreateAccountOnDelete,
	current_protocol_version
	) {
	let sender_is_receiver = account_id == &delete_account.beneficiary_id;
	let is_receiver_implicit =
	is_implicit_account_creation_enabled(current_protocol_version)
	&& is_account_id_64_len_hex(&delete_account.beneficiary_id);
	let exec_gas = config.action_receipt_creation_config.send_fee(sender_is_receiver)
	+ transfer_send_fee(
	&config.action_creation_config,
	sender_is_receiver,
	is_receiver_implicit,
	);
	result.gas_burnt += exec_gas;
	result.gas_used += exec_gas
	+ config.action_receipt_creation_config.exec_fee()
	+ transfer_exec_fee(&config.action_creation_config, is_receiver_implicit);
	result.new_receipts.push(Receipt {
	predecessor_id: account_id.clone(),
	receiver_id: delete_account.beneficiary_id.clone(),
	// Actual receipt ID is set in the Runtime.apply_action_receipt(...) in the
	// "Generating receipt IDs" section
	receipt_id: CryptoHash::default(),
	receipt: ReceiptEnum::Action(ActionReceipt {
	signer_id: action_receipt.signer_id.clone(),
	signer_public_key: action_receipt.signer_public_key.clone(),
	gas_price: action_receipt.gas_price,
	output_data_receivers: vec![],
	input_data_ids: vec![],
	actions: vec![Action::Transfer(TransferAction { deposit: account_balance })],
	}),
	});
	} else {
	result
	.new_receipts
	.push(Receipt::new_balance_refund(&delete_account.beneficiary_id, account_balance));
	}

This seem to use a regular transfer action receipt, so Indexer for Explorer should be fine.

[frol]

@bowenwang1996 I suggest we stabilize features the week before we cut a release.