[Backport 13.0] In ResourceResolver bean configuration, variables defined in hst.properties cannot be expanded

It's impossible to use a variable interpolation expression in crisp resource resolver bean definition at the moment. It's sometimes inconvenient to define all the params only in the crisp:paramnames and crisp:paramvalues in repository. It's also inconvenient to sys admins as they always need to access cms console and update those manually for each env.

Note: the app context for the crisp resource resolver bean does not inherit from neither HST container component manager's context nor HST module instance's context. As a result, it cannot be aware of ComponentManager nor container configuration. This limitation is by design as we don't want to give power to the crisp resource resolver context beans to access hst container beans fully.