Ship search target numbers excessively low with Campaign Operations rating system

[SuperStucco]

Similar to #3729, doing a ship search with the Campaign Operations overall unit rating is blowing out the numbers with a long running campaign. Due to the calculation using the uncapped Campaign Operations rating number, as opposed to the old Field Manual: Mercenaries fixed values, it ends up with vastly off-base target numbers:

mekhq/MekHQ/src/mekhq/campaign/market/PersonnelMarket.java

Lines 401 to 416 in 48b1432

	public TargetRoll getShipSearchTarget(Campaign campaign, boolean jumpship) {
	TargetRoll target = new TargetRoll(jumpship ? 12 : 10, "Base");
	Person adminLog = campaign.findBestInRole(PersonnelRole.ADMINISTRATOR_LOGISTICS, SkillType.S_ADMIN);
	int adminLogExp = (adminLog == null) ? SkillType.EXP_ULTRA_GREEN
	: adminLog.getSkill(SkillType.S_ADMIN).getExperienceLevel();
	for (Person p : campaign.getAdmins()) {
	if ((p.getPrimaryRole().isAdministratorLogistics() || p.getSecondaryRole().isAdministratorLogistics())
	&& p.getSkill(SkillType.S_ADMIN).getExperienceLevel() > adminLogExp) {
	adminLogExp = p.getSkill(SkillType.S_ADMIN).getExperienceLevel();
	}
	}
	target.addModifier(SkillType.EXP_REGULAR - adminLogExp, "Admin/Logistics");
	target.addModifier(IUnitRating.DRAGOON_C - campaign.getUnitRatingMod(), "Unit Rating");
	return target;
	}
	}

As with #3729 this could be handled with clamping the rating value to the Dragoon rating enums, or separate calculations for the two unit rating systems.

[pheonixstorm]

CO uses a different formula for calculating availability for Large Craft. CO p17

CO also does not care about Logistics, Command, etc admin or unit rating.

AtB was not designed for use with CO rules at all as it wasn't even released at the time AtB as a ruleset was written. The code for AtB was designed the same way for the most part. At some point Stratcon may change that but that is a question for @NickAragua