[ET-VK] Adding source_offset processing to copy_packed_dim_offset function.

[trivedivivek]

Stack from ghstack (oldest at bottom):

• [ET-VK] Adding all tensor packing support to split op. #9345
• -> [ET-VK] Adding source_offset processing to copy_packed_dim_offset function. #9344
• [ET-VK] Adding boolean parameters to add_copy_offset_node to specify index calculation function in copy op's shader. #9343
• [ET-VK] Adding all tensor packing support to cat op. #9331
• [ET-VK] Minor performance improvement to permute op. #9330

This diff change copy_packed_dim_offset function and associated shader to handle the source_offset parameter.
This change will help enable all tensor packing for slice op.

Differential Revision: D71349217

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/9344

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 1 Cancelled Job, 1 Unrelated Failure

As of commit 8b16139 with merge base 206a4df ():

NEW FAILURES - The following jobs have failed:

• Check Labels / Check labels (gh)
  RuntimeError: Error checking labels: PR does not have required labels
• pull / unittest-buck / linux / linux-job (gh)
  RuntimeError: Command docker exec -t d43be25851e18b8d275afa0ee52758a3888c6ca8a69f4893ae25ce95810f74d8 /exec failed with exit code 3

CANCELLED JOB - The following job was cancelled. Please retry:

• pull / unittest / macos / macos-job (gh)
  ##[error]The operation was canceled.

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest-buck / macos / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 3

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D71349217

[github-actions]

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.