Send path when resolving actions

[thboop]

This PR sends up the path in the resolve actions endpoint so we can properly validate policy when JIT downloading Composite Actions

[ericsciple]

nit: consider deleting the comment on this method (line 595)

[ericsciple]

discussed offline... example:

my-org/my-repo/my-folder/my-subfolder@v1

• NameWithOwner: my-org/my-repo
• Ref: v1
• Path my-folder/my-subfolder

[KyleJamesWalker]

@thboop or @ericsciple do you think this would be causing our composite actions to be erroring out now?

It was working yesterday just fine, and now we're seeing:

Error: `uses:` keyword is not currently supported.

I noticed this was part of the release that came out 4 hours ago, we are using a composite action with uses clauses.

The uses clause wasn't perfect but we found a workout for our flow and were relying on.

Example:

    - name: Manually checkout all actions for easy usage
      shell: bash
      run: |
        mkdir -p actions
        git clone https://github.com/mikefarah/yq --depth 1 -b v4.11.2 actions/yq
        # Additional actions followed

    - name: Update chart values with built tag [helm]
      # uses: mikefarah/yq@v4.11.2
      uses: ./actions/yq
      with:
        cmd: yq ...

[thboop]

@KyleJamesWalker were you using custom self hosted runnners by any chance? Composite should never have been enabled for public use on github.com. That being said, we plan to ship the feature in the very near future.

[KyleJamesWalker]

@thboop thanks, good to know. Can't wait for this feature, it would be extremely helpful to use Github Actions in our release workflow.

We're using public runners (not self-hosted), not sure if it matters any but we are also on GitHub enterprise.

[KyleJamesWalker]

In case anyone looks at this later it is now fully working as expected: #646 (comment)