fix(flyteidl2): rename ActionMetadata.funtion_name to function_name

[vipulbhasin23]

Tracking issue

Related to #7558

Why are the changes needed?

ActionMetadata.funtion_name has a typo in its field name (missing "c"). This PR fixes the spelling to function_name across the proto definition and the one backend Go file that references it.

This covers Parts 1-3 of #7558 (proto rename, backend Go usages) as scoped by the issue itself, which calls this out as a complete, standalone contribution. Part 4 (bumping the flyteidl2 dependency in flyteorg/flyte-sdk) is a separate repo and is currently blocked on a new package release, so it's left as a follow-up for a separate PR/contributor.

What changes were proposed in this pull request?

• Renamed the proto field ActionMetadata.funtion_name to function_name in flyteidl2/workflow/run_definition.proto (field number 13 unchanged, so this is wire-compatible).
• Updated the two call sites in runs/service/run_service.go (actionMetadataFromModel and convertNodeUpdateToEnrichedProto) to use the corrected FunctionName field name.
• Generated stubs under gen/ are intentionally not hand-edited in this PR — commenting /regen on this PR will trigger CI to regenerate them.

How was this patch tested?

• go build ./runs/... (will fail until /regen runs, since the generated struct still has the old field name — expected).
• grep -rn "funtion" . | grep -v "/gen/" returns nothing.

Labels

changed

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

Stack

Docs link

[vipulbhasin23]

/regen

[vipulbhasin23]

The /regen workflow failed: https://github.com/flyteorg/flyte/actions/runs/29914379379

Looking at the logs, the Checkout code step in .github/workflows/regenerate-on-comment.yml checks out repository: flyteorg/flyte with ref: <PR head ref>, but this PR's branch (fix/rename-funtion-name-typo) only exists on my fork (vipulbhasin23/flyte), not on flyteorg/flyte itself:

Syncing repository: flyteorg/flyte
...
fatal: A branch or tag with the name 'fix/rename-funtion-name-typo' could not be found

It looks like the workflow doesn't currently handle PRs opened from forks (it would need to check out pull_request.head.repo rather than assuming the branch lives in the base repo). Since I don't have write access to trigger this myself, could a maintainer either:

• run the regen manually and push the resulting gen/ changes to this branch, or
• point me to the right way to get the stubs regenerated as an external contributor?

Happy to make the manual edits under gen/ myself if that's preferred instead.

[vipulbhasin23]

conflict resolved, regenerated stubs verified clean, ready for workflow approval and review whenever a maintainer has a moment.