test-validator: Verify program ELFs

[acheroncrypto]

Problem

solana-test-validator doesn't check whether program ELFs are valid before appending their data to the program data accounts:

agave/test-validator/src/lib.rs

Lines 798 to 808 in 3deac72

	let data = solana_program_test::read_file(&upgradeable_program.program_path);
	let (programdata_address, _) = Pubkey::find_program_address(
	&[upgradeable_program.program_id.as_ref()],
	&upgradeable_program.loader,
	);
	let mut program_data = bincode::serialize(&UpgradeableLoaderState::ProgramData {
	slot: 0,
	upgrade_authority_address: Some(upgradeable_program.upgrade_authority),
	})
	.unwrap();
	program_data.extend_from_slice(&data);

Summary of changes

Verify program ELFs before adding program data accounts to the genesis configuration.

With this change, the behavior with an invalid program ELF is the same as the solana program deploy command. An example output of trying to load an invalid ELF (with mutable static data):

Error: failed to start validator: ELF error: ELF error: Failed to parse ELF file: Section or symbol name `.bss._ZN6native7` is longer than `16` bytes

Fixes #4191

[acheroncrypto]

This duplicates a similar logic below:

agave/test-validator/src/lib.rs

Lines 859 to 870 in 3deac72

	// Only activate features which are not explicitly deactivated.
	let mut feature_set = FeatureSet::default().inactive;
	for feature in &config.deactivate_feature_set {
	if feature_set.remove(feature) {
	info!("Feature for {:?} deactivated", feature)
	} else {
	warn!(
	"Feature {:?} set for deactivation is not a known Feature public key",
	feature,
	)
	}
	}

I wanted to avoid making changes to the existing code to make it easier to review. Would it be better to refactor this to avoid duplicating the logic, or should I keep it as is?