release-name-template from config file is silently ignored by cr upload

Setting release-name-template in a config file passed via --config has no effect on cr upload. The release is always created using the pflag default template _{{ .Name}}-{{ .Version }}_, regardless of the config file value.

### Steps to Reproduce

1. Create a config file (.github/cr.yaml):
owner: myorg
git-repo: myrepo
skip-existing: true
release-name-template: "v{{ .Version }}"

2. Package a chart (name: myrepo, version: 0.1.0):
cr package chart/ --package-path .cr-release-packages

3. Upload with the config file:
cr upload -o myorg -r myrepo -c --config .github/cr.yaml

### Expected Behavior

Release created with tag and name v0.1.0 (from release-name-template: "_v{{ .Version }}_").

### Actual Behavior

Release created with tag and name myrepo-0.1.0 (from the pflag default _{{ .Name }}-{{ .Version }}_). The config file value is silently ignored.

Start at the cr upload command's config-loading and release-name-template flag handling, then reproduce the example with the provided .github/cr.yaml configuration. Trace why the config value is ignored in favor of the pflag default and verify that the resulting release tag and name use the configured template.

Written by the indexing model from the issue text.