feat(apify): add decryption for input secrets

[drobnikj]

Implementation for decryption of input secrets.

• move APIFY_INPUT_SECRETS_PRIVATE_KEY_PASSPHRASE and APIFY_INPUT_SECRETS_PRIVATE_KEY_FILE into @apify/consts

I still didn't comment or document the secrets at all, I would do it once we test it internally in team and release it into public.

[fnesveda]

Looks good! I found just one small thing.

[fnesveda]

I think these should stay here, no? They're used in the e2e tests.

[B4nan]

Lets see if it breaks it, they are still in the lock file, and as long as we dont directly import them in the tests, they dont have to be specified here.

E2E tests for this branch running here: https://github.com/apify/apify-sdk-js/actions/runs/3203931243

[fnesveda]

I think it's gonna work, since they're still in the lockfile, but they're imported from the scraper source code, which is then imported dynamically through here:

apify-sdk-js/test/e2e/tools.mjs

Line 58 in 6d1af79

await import(`../../packages/actor-scraper/${scraper}/dist/main.js`);

But I don't know how it works with the workspaces, if you reference a workspace which has them listed as dependencies, maybe you don't need to list them as your own dependencies? I guess it's fine in that case then.

[drobnikj]

Test passed so it should be fine.