Provide an optional Profile to the verification key strategy

[yvgny]

PR #2235 has just been merged, but I realized that not having access to Profile could be too restrictive. For example, accessing storage with the current function's signature is hard. In fact, I thought that custom strategies could be initialized with an InjectionContext and query what they need, but it doesn't seem to be working. Let me know if there is a more idiomatic way of doing this.

This PR fixes this by providing an optional Profile and switching to an async method.

[swcurran]

Given this is related to #2235 -- do we need this one to be merged as part of 0.8.2? @dbluhm @usingtechnology , could you please take a look at this one and let us know?

Thanks!

[dbluhm]

I think it would be better to require the profile and just not use it if the strategy does not require it. This will make the calls to the strategy more consistent and prevent intermittent failures from one call not having it but others do.

[usingtechnology]

I agree with @dbluhm.

[yvgny]

Done

[dbluhm]

Yes, ideally this is merged with 0.8.2 if we can swing it.

[usingtechnology]

I agree that the profile should NOT be optional and let the implementations decide if it needs to use it.

Also, you need to update all the docstrings with the new parameter.

[usingtechnology]

I agree with @dbluhm.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information