Add enable/disable deploying in-memory JWKS Api and Fix block subscription for production only bug

[nisan-abeywickrama]

Purpose

• Provide the configuration support to disable the deployment of the in memory JWKS api.
• Update Unit tests to include the updated config for JWKS api enabling/disabling
• Fix sandbox invocation using API key is blocked when subscription is blocked for production only.
• Currently instead of key type, application token type is used to determine if the API key is production or sandbox type in the above condition giving the incorrect behaviour.
• Fixes API key not working as expected when production is blocked  api-manager#3136
• Fixes Need to provide capability to disable JWKS endpoint api-manager#3395

Implementation

• Add EnableJWKSApi configuration constant to enable/disable JWKS Api
• Using the set configuration value check the condition if to deploy the JWKS Api
• Add default value to EnableJWKSApi configuration in amConfig.xml
• Mock the method call chain in DefaultAPIHandlerTest to retrieve the above configuration value using the method isJWKSApiEnabled
• Pass keyType to AbstractKeyValidationHandler from GatewayUtils through the value extracted from the API key payload to fix the 'block subscription for production only' applying to sandbox API key.

Additional Notes

• This PR includes a fix for an intermittent failure in testGetAPIRevisionDeploymentsByWorkflowStatusAndApiUUID unit test
• The failure occurs due to the expected order with testUpdateAPIRevisionDeploymentStatus test where the above test case should run before this (JUnit does not run test cases in the order of the code written [1]).
• To fix this issue, these two test cases were combined to a single test case

[1] - https://junit.org/junit5/docs/current/user-guide/#writing-tests-test-execution-order