if we store 20kb of test asset in the repo = extra 20kb will be downloaded each time a user uses the step
storing this type of test assets in the repo is not the best approach as we need(should) to check multiple combinations of cases and that would mean extra file per test case = extra unusable data downloaded - btw multi use cases should be covered by asset generation rather than storing each asset separately
creating keychain and p12 files implementation could be moved out from the test case to helper functions
Updated to test potential issues in https://bitrise.atlassian.net/browse/TOOL-1376 are not present. Passwords with special chars are not and issue, and it is redacted in logs.