SECRETS: Don't limit the global number of ccaches
    
    Related:
    https://pagure.io/SSSD/sssd/issue/3386
    
    In the KCM context, the global number of ccaches would limit the number
    of users who can store their ccaches in the KCM deamon.
    
    In more detail, the options have the following semantics with KCM:
        - DEFAULT_SEC_KCM_MAX_SECRETS - global number of secrets, would
        cover both how many ccaches can a user store, but this is better
        served with DEFAULT_SEC_KCM_MAX_UID_SECRETS
    
        - DEFAULT_SEC_KCM_MAX_UID_SECRETS - how many 'principals' can a user
        kinit with
    
        - DEFAULT_SEC_KCM_MAX_PAYLOAD_SIZE - the payload size of service
        tickets
    
    With the above in mind, I think the most important limits are
    max_uid_secrets to limit and the payload size to constraint how much
    space can a user occupy and it doesn't make much sense to limit the
    global quota.
    
    Reviewed-by: Michal Židek <mzidek@redhat.com>