Update the config origin metric to match what it's mapping (#9045)

Author: sezen-datadog

internal-api/src/main/java/datadog/trace/api/ConfigOrigin.java

@@ -1,5 +1,7 @@
 package datadog.trace.api;
 
+// https://github.com/DataDog/instrumentation-telemetry-api-docs/blob/main/
+// GeneratedDocumentation/ApiDocs/v2/SchemaDocumentation/Schemas/conf_key_value.md
 public enum ConfigOrigin {
   /** configurations that are set through environment variables */
   ENV("env_var"),
@@ -11,6 +13,12 @@ public enum ConfigOrigin {
   LOCAL_STABLE_CONFIG("local_stable_config"),
   /** configuration read in the stable config file, managed by fleet */
   FLEET_STABLE_CONFIG("fleet_stable_config"),
+  /** configurations that are set through the customer application */
+  CODE("code"),
+  /** set by the dd.yaml file or json */
+  DD_CONFIG("dd_config"),
+  /** set for cases where it is difficult/not possible to determine the source of a config. */
+  UNKNOWN("unknown"),
   /** set when the user has not set any configuration for the key (defaults to a value) */
   DEFAULT("default");