ActionExecutionFunction are re-computed for an incremental build

### Description of the bug:

Previously, when you do an incremental build immediately (i.e. no changes to the source or output files) after a clean build, you would expect no actions are executed.

However, with Bazel 7, we can see many ActionExecutionFunctions are re-computed in the profile.

### Which category does this issue belong to?

Local Execution

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

1. Clone `https://github.com/bazelbuild/bazel`
2. Repro: `bazel clean && bazel build --nouse_action_cache --disk_cache= //src:bazel && bazel build --nouse_action_cache --disk_cache= //src:bazel`
3. Notice the second incremental build hits disk cache, not the skyframe inmemory cache.

### Which operating system are you running Bazel on?

Linux

### What is the output of `bazel info release`?

7.1.0

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

_No response_

### Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_