Fix: Clarify workspace instead of environment for Dynamic Plugin Orde…

…ring feature (#7745)

Clarify workspace instead of environment

According to tests, this seems to be unique to each workspace. In other words, one workspace can still use dynamic ordering if consumer-scoped plugins are in use as long as the consumer-scoped plugins are in a different workspace than the one using dynamic ordering for example. This created confusion with a customer and required manual testing.

app/_src/gateway/kong-enterprise/plugin-ordering/index.md

@@ -61,7 +61,7 @@ PluginA:
 
 Dynamic plugin ordering cannot coexist with consumer-scoped plugins, 
 even if they are applied to entirely different service and route pairs or are running globally.
-If you have consumer-scoped plugins anywhere in your environment, you can't use
+If you have consumer-scoped plugins anywhere in your workspace, you can't use
 dynamic plugin ordering.
 
 Consumer mapping and dynamic plugin ordering both run in the access phase, but the order of the