Disable missing key warnings when expected

[IvoDD]

• Sets opts.dont_warn_about_missing_key=true when missing keys are expected (For example when writing a previously missing symbol it is expected to try to read a missing ref key)

Reference Issues/PRs

What does this implement or fix?

Any other comments?

Checklist

Checklist for code changes...

• Have you updated the relevant docstrings, documentation and copyright notice?
• Is this contribution tested against all ArcticDB's features?
• Do all exceptions introduced raise appropriate error messages?
• Are API changes highlighted in the PR description?
• Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?

[muhammadhamzasajjad]

@IvoDD, whatever fix you decide to use, please ensure that it is consistent between all the storages. Currently, you are removing the warning only from s3, but the same warning is also logged in other storages. If you decide to stick with this solution, please remove the warning from other storages too.

Instead if you decide to set opts.dont_warn_about_missing_key to true as a solution, then the behaviour should already be consistent between the storages.

[poodlewars]

As discussed in Slack let's set opts.dont_warn_about_missing_key=true on read_symbol_ref and leave the storage backends untouched. I'm assuming that read_symbol_ref is the only additional place we wish to suppress the warning, but worth checking if we should add it elsewhere too.