Registered binders not iterated in registration order

[eocantu]

In our migration from jersey 2.25.1 to 2.32 we have noticed that the way in which registered binders are iterated is no longer deterministic. This is particularly problematic when different configuration order could lead to the wrong thing getting injected.

A similar issue was raised in #4538 but it doesn't seem like the fix addresses the issue for binders.

It seems to me the problem lies in the following code:

jersey/core-common/src/main/java/org/glassfish/jersey/model/internal/ComponentBag.java

Lines 603 to 611 in aebe70d

	public Set<Object> getInstances(final Predicate<ContractProvider> filter) {
	return instancesView.stream()
	.filter(input -> {
	final ContractProvider model = getModel(input.getClass());
	return filter.test(model);
	})
	.collect(Collectors.toSet());
	}

instances was originally created as a LinkedHashSet which is an ordered set, but the method above uses Collectors.toSet() which doesn't preserve order.

[jansupol]

Fixed by #4648