[processor/resourcedetection] support for periodically do detect action

[JaredTan95]

Component(s)

processor/resourcedetection

Is your feature request related to a problem? Please describe.

When user is using consul detector and the resource attributes of consul changed, otel col will still using out-dated attributes unless restart otel col.

Describe the solution you'd like

1. Add an optionnal configuration for detection to periodically invoke the detect action:

opentelemetry-collector-contrib/processor/resourcedetectionprocessor/config.go

Line 43 in 3099e8e

Attributes []string `mapstructure:"attributes"`

type Config struct {
	Attributes []string `mapstructure:"attributes"`
+	// interval of detect action
+	DetectInterval time.Duration `mapstructure:"detect_interval"`
}

2. Update the start logical with TimeTicker to get resource attributes if DetectInterval great than 0ms
   

   opentelemetry-collector-contrib/processor/resourcedetectionprocessor/resourcedetection_processor.go

   Line 33 in 3099e8e

   rdp.resource, rdp.schemaURL, err = rdp.provider.Get(ctx, client)

	client, _ := rdp.httpClientSettings.ToClient(ctx, host, rdp.telemetrySettings)
	ctx = internal.ContextWithClient(ctx, client)
	var err error
+      //TODO: only create ticker if `DetectInterval` great than `0ms`
+	intervalTicker := time.NewTicker(rdp.detectInterval)
+	defer intervalTicker.Stop()
+
+	for range intervalTicker.C {
+		rdp.resource, rdp.schemaURL, err = rdp.provider.Get(ctx, client)
+		if err != nil {
+			rdp.telemetrySettings.Logger.Error("failed to retrieve resource from provider: %v", zap.Error(err))
+		}
+	}

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• processor/resourcedetection: @Aneurysm9 @dashpole

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• processor/resourcedetection: @Aneurysm9 @dashpole

See Adding Labels via Comments if you do not have permissions to add labels yourself.