[fix 13327] ignore HTTPRoute .status.parents re-ordering

[DerekTBrown]

Commit Message:

[fix 13327] ignore HTTPRoute .status.parents re-ordering

The `eq_time_insensitive_route_parent_statuses` considers ordering when comparing statuses, even though ordering
doesn't matter. This can result in infite update loops.

Add logic to `eq_time_insensitive_route_parent_statuses` to pre-sort statuses before comparison, thus making the result independent of ordering.

A unit test was added to validate the fix.

Fixes #13327

[olix0r]

Do we need the same treatment for the conditions comparison?

linkerd2/policy-controller/k8s/status/src/index.rs

Lines 1538 to 1553 in 8265134

	fn eq_time_insensitive_conditions(
	left: &[k8s_core_api::Condition],
	right: &[k8s_core_api::Condition],
	) -> bool {
	if left.len() != right.len() {
	return false;
	}
	left.iter().zip(right.iter()).all(|(l, r)| {
	l.message == r.message
	&& l.observed_generation == r.observed_generation
	&& l.reason == r.reason
	&& l.status == r.status
	&& l.type_ == r.type_
	})
	}

[DerekTBrown]

Do we need the same treatment for the conditions comparison?

AFAIK, K8s preserves the order of lists in the HTTPRoute resource. The order of status.parents isn't guaranteed because multiple controllers could be modifying status.parents, and there isn't a contract between the controllers as to ordering. However, status.parents[(controllerName==linkerd.io/policy-controller)].conditions shouldn't be modified by outside controllers, so I don't think we strictly need to do order invariant comparison (since it should be in the order expected by linkerd).

All that said, it can't hurt (besides a little added complexity) to do order invariant comparison for conditions as well.

Up to you- happy to extend to cover conditions as well.

[olix0r]

Thanks!