regression: parsePush writes to its own module's dir instead of the process root

[coopernetes]

Prior to e3ee26a , parsePush would create a temporary directory & checkout a repo to the main process's working directory + .tmp/{timestamp}. After that refactor, the action attempts to instead write to its own module's directory (${process_root}/src/proxy/processors/push-action/.tmp). In secure environments where file permissions are minimal, it leads to the following error:

Error: EACCES: permission denied, mkdir '/app/src/proxy/processors/push-action/.tmp'
    at Object.mkdirSync (node:fs:1372:26)
    at /app/src/proxy/processors/push-action/parsePush.ts:2:1529
    at Object.<anonymous> (/app/src/proxy/processors/push-action/parsePush.ts:3:3)
    at Module._compile (node:internal/modules/cjs/loader:1529:14)
    at Object.transformer (/app/node_modules/tsx/dist/register-D46fvsV_.cjs:3:1104)
    at Module.load (node:internal/modules/cjs/loader:1275:32)
    at Module._load (node:internal/modules/cjs/loader:1096:12)

git-proxy/src/proxy/processors/push-action/parsePush.ts

Line 9 in e3ee26a

const dir = path.resolve(__dirname, './.tmp');

Suggest restoring the prior behaviour unless there is some reason why that change was made that I haven't accounted for.

[jescalada]

@coopernetes I totally missed that scenario! Originally I meant to keep the temp files isolated and prevent tests/other files from overwriting each other's temp stuff. But now that I searched around, I realize that parsePush.ts is the only place we use .tmp.

Will make a PR for this ASAP 🚀