chore(publish): [v8] Use craft config from merge target branch for release preparation (#10764)

We also change the `develop` release action  to take
the craft config from `master` because technically, our default branch is
`develop` and the config _could_ diverge. Unlikely but still something
I'd say we should do now that we can.

Author: Lms24

.github/workflows/auto-release.yml

@@ -36,3 +36,4 @@ jobs:
           version: ${{ steps.version.outputs.group1 }}
           force: false
           merge_target: master
+          craft_config_from_merge_target: true

.github/workflows/release.yml

@@ -29,3 +29,5 @@ jobs:
           version: ${{ github.event.inputs.version }}
           force: ${{ github.event.inputs.force }}
           merge_target: ${{ github.event.inputs.merge_target }}
+          craft_config_from_merge_target: true
+