docs(godot): Document environment variable fallbacks for release and environment

docs/platforms/godot/configuration/environments.mdx

@@ -12,4 +12,6 @@ Environments are case-sensitive. The environment name can't contain newlines, sp
 
 <PlatformContent includePath="set-environment" />
 
+If you do not set `environment` explicitly, the SDK will check for the `SENTRY_ENVIRONMENT` environment variable. If that is also not set, the SDK will automatically detect the environment based on the current runtime context.
+
 Environments help you better filter issues, releases, and user feedback in the Issue Details page of sentry.io, which you learn more about in our [documentation that covers using environments](/product/sentry-basics/environments/).

docs/platforms/godot/configuration/options.mdx

@@ -42,7 +42,7 @@ Specifies the minimum level of messages to be printed if `debug` is turned on. P
 
 <SdkOption name="release" type="string" envVar="SENTRY_RELEASE">
 
-Release version of the application. This value must be unique across all projects in your organization. By default, the SDK reads from the `application/config/name` and `application/config/version` project settings to generate the release identifier in the format `"{app_name}@{app_version}"`. Alternatively, you can set `release` to a custom value [programmatically](#programmatic-configuration), optionally using the `{app_name}` and `{app_version}` placeholders.
+Release version of the application. This value must be unique across all projects in your organization. If not set explicitly, the SDK will try to read this value from the `SENTRY_RELEASE` environment variable. Otherwise, the SDK reads from the `application/config/name` and `application/config/version` project settings to generate the release identifier in the format `"{app_name}@{app_version}"`. You can also set `release` to a custom value [programmatically](#programmatic-configuration), optionally using the `{app_name}` and `{app_version}` placeholders.
 
 Release names are strings, but some formats are detected by Sentry and might be rendered differently. Learn more about how to send release data so Sentry can tell you about regressions between releases and identify the potential source in [the releases documentation](/product/releases/) or the <SandboxLink scenario="releases">sandbox</SandboxLink>.
 
@@ -58,7 +58,7 @@ Sets the distribution of the application. Distributions are used to disambiguate
 
 Sets the environment. Environments indicate where an error occurred, such as in a release export, headless server, QA build, or another deployment. A release can be associated with more than one environment to separate them in the UI (think `staging` vs `production` or similar).
 
-This option defaults to `{auto}`, which automatically detects the environment based on the current runtime context and sets it to one of the following values: `editor_dev`, `editor_dev_run`, `export_debug`, `export_release`, or `dedicated_server`.
+If not set explicitly, the SDK will try to read this value from the `SENTRY_ENVIRONMENT` environment variable. Otherwise, this option defaults to `{auto}`, which automatically detects the environment based on the current runtime context and sets it to one of the following values: `editor_dev`, `editor_dev_run`, `export_debug`, `export_release`, or `dedicated_server`.
 
 </SdkOption>