Process profiles in filter phase

[MikeEdgar]

For quarkusio/quarkus#53479

This change moves the handling of operation profiles to the filter phase, allowing operations contributed to the model from a static file or OASModelReader to be included/excluded according to any given configurations.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
98.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[phillip-kruger]

LGTM

[MikeEdgar]

@Azquelt I don't recall if you were curious to look at this one. I'll be looking to do a release in the next day or two, so please let me know if you'd like some additional time to go over it.

[Azquelt]

This looks a bit sketchy. Can the user specify both and include list and an exclude list?

It's odd that the include list is ignored completely if the exclude list is specified.

I realise this logic has not changed.

[MikeEdgar]

Good point, I agree on that. Maybe something like this would be better (plus updating the test). Both include and exclude could be specified.

public static boolean includedProfile(Extensible<?> extensible, Set<String> included, Set<String> excluded) {
    Set<String> profiles = getProfiles(extensible);

    if (profiles.isEmpty()) {
        // Include an extensible without any profiles attached when none
        // are explicitly included via configuration.
        return included.isEmpty();
    }

    if (included.stream().anyMatch(profiles::contains)) {
        return true;
    }

    if (excluded.stream().anyMatch(profiles::contains)) {
        // Exclude the extensible if it has configured exclusions and also
        // does not have any configured inclusions. This also means that
        // inclusion overrides exclusion if a profile is configured for both.
        return false;
    }

    return included.isEmpty();
}