Roles ranges, when used for permissions, were not accounting for NOT ranges

The ability to permission "Summary Page (version 2)" type Scripts based on a range of Roles was recently added (this has the advantage of working when signed in as an Administrator, unlike Permission Keys).

However, it was found that the business layer function to check for Role membership based on a range was not working for NOT ranges, e.g., "!TEST" (this should make the Summary Page available to every User unless they are in the TEST Role).

To prevent unintentionally breaking existing functionality, a new parameter to check for exclusion ranges has been added to finBL.CurrentUserInformation.IsInRolesRange.

Currently, this additional parameter is only used from finScriptRO.HasPermissionToExecute.

NOTE: The finPOWER Connect Cloud Configuration form allows many aspects of finPOWER Connect Cloud the be controlled via Roles Ranges. Currently, these do not respect exclusion ranges.