fix: pull registry-aware image name on local miss

When `image-repo` is overridden, the registry plugin pushes under that name and
the bare local `dokku/<app>:N` tag is never created. `fn-verify-app-image` now
queries the `deployed-app-image-repo` trigger and pulls `${REMOTE_REPO}${DEPLOYED_REPO}:${TAG}`,
retagging it as the local bare reference so subsequent inspects resolve. Also
aligns the `storage:ensure-directory` deprecation test assertion with the
standardized `Deprecated:` prefix.

tests/unit/registry_2.bats

@@ -105,8 +105,16 @@ setup_push_on_release_app() {
   run /bin/bash -c "dokku config:set $TEST_APP RECOVERY_KEY=value"
   echo "output: $output"
   echo "status: $status"
+  assert_success
   # triggerRestart forwards the deployed numeric tag (not "latest") to
   # release-and-deploy, so the wrapper attempts recovery against ":1" rather
   # than skipping recovery for ":latest" which is never pushed.
   assert_output_contains "dokku/$TEST_APP:1 not found locally, pulling from registry"
+
+  # The wrapper retags the registry image back to the bare local name so
+  # subsequent get_app_image_name inspects resolve.
+  run /bin/bash -c "docker image inspect dokku/$TEST_APP:1"
+  echo "output: $output"
+  echo "status: $status"
+  assert_success
 }

tests/unit/storage.bats

@@ -443,7 +443,7 @@ teardown() {
   echo "output: $output"
   echo "status: $status"
   assert_success
-  assert_output_contains "deprecated"
+  assert_output_contains "Deprecated:"
 }
 
 @test "(storage:migrate) leaves legacy-mounts-migrated unset for apps with no legacy -v lines" {