LPS-36021 Alter the column type in a database agnostic way
LPS-35826 The comparisons must always be based on integers.

A side effect of this change is that the class is now effectively ignoring any number after the fourth, but that is fine since it didn't work properly in that case anyway.
LPS-35826 Consider the case of using + in the buildNumber
LPS-35673 Avoid the duplication of asset guery rules in asset publisher due filter search limitations
LPS-35673 source and visual formatting
LPS-35673 Rename to is* for booleans, sort constructor logically the way it is already logically done in the equals method you wrote.
LPS-35673 Sort, and follow pattern in ClusterNode
LPS-35673 Move to portal-service
LPS-35673 It was the equals method that was not sorted right earlier. Proper logical order is contains, andOperator, name, and then values.
LPS-35673 Isn't calling contains on a list the same as iterating through it and checking if a value equals?
LPS-35673 SF