refactor(run/image-processing): replace deprecated gm library with sharp

[angelcaamal]

Description

Fixes internal: b/503844690

Note: Before submitting a pull request, please open an issue for discussion if you are not associated with Google.

Checklist

• I have followed guidelines from CONTRIBUTING.MD and Samples Style Guide
• Tests pass: npm test (see Testing)
• Lint pass: npm run lint (see Style)
• Required CI tests pass (see CI testing)
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• This pull request is from a branch created directly off of GoogleCloudPlatform/nodejs-docs-samples. Not a fork.
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
• This sample adds a new sample directory, and I created GitHub Actions workflow for this sample
• This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
• Please merge this PR for me once it is approved

Note: Any check with (dev), (experimental), or (legacy) can be ignored and should not block your PR from merging (see CI testing).

[gemini-code-assist]

Code Review

This pull request replaces the ImageMagick-based gm library with sharp for image processing and adds a check to prevent recursive execution when events are triggered by the destination bucket. A review comment identifies a potential resource leak because the file cleanup logic is not scoped to cover processing failures, and it points out that fs.unlink is being incorrectly used as a promise-based function instead of fs.promises.unlink.