fix(ui): adjust transform origin in application-resource-tree component

[srikanth597]

Closes #19519

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[bunnyshell]

❗ Preview Environment delete from Bunnyshell failed

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

• 🚀 /bns:deploy to redeploy the environment
• ❌ /bns:delete to try again to remove the environment

[bunnyshell]

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[srikanth597]

Tested On a Regular device of 15-16 inches

[srikanth597]

Tested on Monitor

[nitishfy]

Please sign the commits.

[srikanth597]

Hi @nitishfy I am not sure if I have understood it correctly, but I have already signed the commits in the new PR, is that not correct?

[crenshaw-dev]

@srikanth597 the naming is unfortunate. "Signed commits" are cryptographically signed (which you've done). "Signed-off commits" just have an extra bit of text on the commit message. You can check the details of the failed "DCO" check for instructions on how to sign off commits.

[nitishfy]

Hi @nitishfy I am not sure if I have understood it correctly, but I have already signed the commits in the new PR, is that not correct?

Simply ammend it using git commit --amend --signoff command

[bunnyshell]

✅ Preview Environment deployed on Bunnyshell

Component	Endpoints
argocd	https://argocd-qhpd5x.bunnyenv.com/
argocd-ttyd	https://argocd-web-cli-qhpd5x.bunnyenv.com/

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

• 🔴 /bns:stop to stop the environment
• 🚀 /bns:deploy to redeploy the environment
• ❌ /bns:delete to remove the environment

[bunnyshell]

✅ Preview Environment created on Bunnyshell but will not be auto-deployed

See: Environment Details

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[srikanth597]

@nitishfy i have cleared the DCO check

[nitishfy]

LGTM!