Resetting useDbConfig attribute in runtime config that was erroneously p...

...ersistent between multiple finds performed against a given model.

In afterFind, the runtime config's useDbConfig attribute is the flag that indicates there are cached results to be returned. However, that attribute was never being reset even though the runtime config is persistent through the lifetime of the behavior, which may involve multiple calls to a model's find methods. If multiple find requests were performed in the same model in the same HTTP request, the useDbConfig attribute could get stuck and would prevent the results all but the first of any given model's find from being cached.