fix: adjust the execution priority of request-id to fix opentelemetry has no request id

[jagerzhang]

Description

Adjust the execution priority of request-id from 11010 to 12015

...
  - request-id                     # priority: 12015
  - zipkin                            # priority: 12011
  #- skywalking                  # priority: 12010
  #- opentelemetry            # priority: 12009
...

Fixes #7239

Checklist

• [✔] I have explained the need for this PR and the problem it solves
• [✔] I have explained the changes or the new features added to this PR
• [✔] I have added tests corresponding to this change
• [✖] I have updated the documentation to reflect this change
• [✖] I have verified that this change is backward compatible (If not, please discuss on the APISIX mailing list first)

[tokers]

I think it's not a good idea to set it adjacent to the request-id plugin. It's not extendable if we need to insert another plugin between them in the future.

[jagerzhang]

I think it's not a good idea to set it adjacent to the request-id plugin. It's not extendable if we need to insert another plugin between them in the future.

OK, already change to 11005

[tzssangglass]

we also need to update the config-default.yaml

[tokers]

@jagerzhang Also, you need to check out the CI failures, we have some test cases to cover the plugin priority settings.

[jagerzhang]

@tokers
CI report this error, I don't know why this file not found.

Error: [error] [lua] config_yaml.lua:72: read_apisix_yaml(): failed to fetch /apisix/t/servroot/conf/apisix.yaml attributes: cannot obtain information from file '/apisix/t/servroot/conf/apisix.yaml': No such file or directory

[tokers]

@tokers CI report this error, I don't know why this file not found.

Error: [error] [lua] config_yaml.lua:72: read_apisix_yaml(): failed to fetch /apisix/t/servroot/conf/apisix.yaml attributes: cannot obtain information from file '/apisix/t/servroot/conf/apisix.yaml': No such file or directory

Looks like this is the actual error: https://github.com/apache/apisix/runs/6977549863?check_suite_focus=true#step:15:700

[jagerzhang]

@tokers I found that the order of plugins will verified in many places, like:

apisix/t/debug/debug-mode.t

Lines 44 to 89 in 69bb8b3

	loaded plugin and sort by priority: 23000 name: real-ip
	loaded plugin and sort by priority: 22000 name: client-control
	loaded plugin and sort by priority: 12011 name: zipkin
	loaded plugin and sort by priority: 12000 name: ext-plugin-pre-req
	loaded plugin and sort by priority: 11010 name: request-id
	loaded plugin and sort by priority: 11000 name: fault-injection
	loaded plugin and sort by priority: 10000 name: serverless-pre-function
	loaded plugin and sort by priority: 4000 name: cors
	loaded plugin and sort by priority: 3000 name: ip-restriction
	loaded plugin and sort by priority: 2990 name: referer-restriction
	loaded plugin and sort by priority: 2900 name: uri-blocker
	loaded plugin and sort by priority: 2800 name: request-validation
	loaded plugin and sort by priority: 2599 name: openid-connect
	loaded plugin and sort by priority: 2555 name: wolf-rbac
	loaded plugin and sort by priority: 2530 name: hmac-auth
	loaded plugin and sort by priority: 2520 name: basic-auth
	loaded plugin and sort by priority: 2510 name: jwt-auth
	loaded plugin and sort by priority: 2500 name: key-auth
	loaded plugin and sort by priority: 2400 name: consumer-restriction
	loaded plugin and sort by priority: 2000 name: authz-keycloak
	loaded plugin and sort by priority: 1010 name: proxy-mirror
	loaded plugin and sort by priority: 1009 name: proxy-cache
	loaded plugin and sort by priority: 1008 name: proxy-rewrite
	loaded plugin and sort by priority: 1005 name: api-breaker
	loaded plugin and sort by priority: 1003 name: limit-conn
	loaded plugin and sort by priority: 1002 name: limit-count
	loaded plugin and sort by priority: 1001 name: limit-req
	loaded plugin and sort by priority: 995 name: gzip
	loaded plugin and sort by priority: 990 name: server-info
	loaded plugin and sort by priority: 966 name: traffic-split
	loaded plugin and sort by priority: 900 name: redirect
	loaded plugin and sort by priority: 899 name: response-rewrite
	loaded plugin and sort by priority: 506 name: grpc-transcode
	loaded plugin and sort by priority: 500 name: prometheus
	loaded plugin and sort by priority: 412 name: echo
	loaded plugin and sort by priority: 410 name: http-logger
	loaded plugin and sort by priority: 406 name: sls-logger
	loaded plugin and sort by priority: 405 name: tcp-logger
	loaded plugin and sort by priority: 403 name: kafka-logger
	loaded plugin and sort by priority: 402 name: rocketmq-logger
	loaded plugin and sort by priority: 401 name: syslog
	loaded plugin and sort by priority: 400 name: udp-logger
	loaded plugin and sort by priority: 398 name: clickhouse-logger
	loaded plugin and sort by priority: 0 name: example-plugin
	loaded plugin and sort by priority: -2000 name: serverless-post-function
	loaded plugin and sort by priority: -3000 name: ext-plugin-post-req

https://github.com/apache/apisix/blob/master/t/admin/plugins.t#L63-L131
https://github.com/apache/apisix/blob/master/conf/config-default.yaml#L335-L410

I think it may be more convenient to uniformly abstract to one place, such as uniformly reading from config-default yaml.

[jagerzhang]

@tokers
Hi，What is the cause of this error:
https://github.com/apache/apisix/runs/6995964208?check_suite_focus=true#step:11:52