get_registered_limits() does not use the Enforcer cache

[melanie witt]

This was missed when the get_registered_limits() method was added after the Enforcer cache had been implemented:

https://github.com/openstack/oslo.limit/commit/bf9deb10c3af4c43f6952f0fcedb9d48dfd8340d

Since caching had been added in _get_limit() and get_registered_limits() does not call _get_limit(), it misses out on caching.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/oslo.limit/+/828813
Committed: https://opendev.org/openstack/oslo.limit/commit/c67c9cf0df47947834b00bc2cbbd4524521bc011
Submitter: "Zuul (22348)"
Branch: master

commit c67c9cf0df47947834b00bc2cbbd4524521bc011
Author: melanie witt <email address hidden>
Date: Fri Feb 11 01:34:41 2022 +0000

    Move Enforcer caching closer to limit retrieval

    In change I22234e0bb6b3a1cecb29a6b99a3afcd02ffdbf5f added a
    get_registered_limits() interface but missed making it work with the
    Enforcer cache because caching was implemented in a higher layer,
    _get_limit() and get_registered_limits() could not make use of
    _get_limit().

    This moves the caching logic to where limits are retrieved from
    keystone, so that get_registered_limits() will use caching and any
    interfaces that might be added in the future will be able to benefit
    from using the cache.

    Closes-Bug: #1964848

    Change-Id: I28cdd4d3f4927b94acea3309b36999850cf2ee2a

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/oslo.limit 1.6.0 release.