Access Management: Allow wildcards in capability scopes

Current access management relies on explicitly defined scopes (spaces, data sets, and tables) that require a full textual match.  As a result, any time a new scope is added, corresponding access lists must be manually updated. 

Supporting wildcards or pattern-based matching when defining access scopes would make this management easier. This would allow access rules to be defined once using predictable naming conventions, rather than requiring explicit enumeration of every individual scope.

For example, if users in GroupA require access to all data originating from the Alpha source system, access rules could be defined using a pattern such as:

alpha:*

Instead of listing each scope individually (e.g. alpha:files:engineering_diagrams, alpha:files:manuals, alpha:time_series:operations).  With this approach, when a new scope like alpha:3d:vessels is introduced, no updates to access lists would be required.