Remove refersion keys from source code

[LenOttSocketMobile]

the refersion keys should NOT be in the checked in code.
maybe add a flag to turn this feature on/off so it can be run as open source?

[LenOttSocketMobile]

Ok, I created a keyvault for the keys.
names are AUrefersion, DEFAULTrefersion, EMEArefersion, GBreferision, JPrefersion
each 'secret' is of the form:
pub_key: "pub_0fa9f9c60fb103ec2c71", sec_key: "sec_e.............", aff_code: "<>"

Happy to discuss other formats....
Paths are:
JP - https://stockcountkeyvault.vault.azure.net/secrets/JPrefersion/3e35b68404ca4e66beb54bfb07c1e824
GB -
https://stockcountkeyvault.vault.azure.net/secrets/GBrefersion/6423997d12e740329ae4cab66c792c56
EMEA - https://stockcountkeyvault.vault.azure.net/secrets/EMEArefersion/b1d54773f03944e99b325f7bc39f819a
AU - https://stockcountkeyvault.vault.azure.net/secrets/AUrefersion/d9e580b2c6a64f5f8c157f1f8f371f40
DEFAULT - https://stockcountkeyvault.vault.azure.net/secrets/DEFAULTrefersion/c797b71419d74eb5bd49498e745b12df

Can be accessed via python, powershell and many other methods. I was assuming these would be grabbed during build? But we could get them at run time...

For now, I have given Shawn's account and the build account read access. But we could give the app access.