fix: split openresty report keys into global and computed pairs

The `openresty:report --format json` payload emitted bare property names for the four global-only properties (`image`, `letsencrypt-email`, `letsencrypt-server`, `allowed-letsencrypt-domains-func-base64`), while `hsts` already used the `global-`/`computed-` convention adopted by the other proxy plugins. External tooling consuming the report had to maintain a per-property naming map within a single plugin. The global flag map now emits `--openresty-global-<X>` (raw stored value, empty when unset) and `--openresty-computed-<X>` (effective value with the built-in default applied) for those four properties plus `hsts`, and the per-app map gains the same pair for the global-only properties. The compose template and the two non-report callers consume the `computed-` accessors so the runtime behavior is unchanged.

plugins/openresty-vhosts/certs-force

@@ -13,7 +13,7 @@ trigger-openresty-vhosts-certs-force() {
     return
   fi
 
-  if [[ -n "$(fn-openresty-letsencrypt-email)" ]]; then
+  if [[ -n "$(fn-openresty-computed-letsencrypt-email)" ]]; then
     echo true
   fi
 }