Honor REST and GraphQL enable flag

[abhishekkumams]

Why make this change?

• Closes Rest and GraphQL enable field is not honored by the runtime engine  #1254
• currently enable/disable flags for the REST/GraphQL in global runtime settings are not honored, and the endpoints are always accessible even when disabled in the config. 

What is this change?

• Adding a check to see if rest/graphQL is disabled, then not mapping the endpoints to the app.
• We discard the requests by throwing the 404 not found error.

How was this tested?

• Integration Tests - Tested for both Hosted and Non-Hosted Scenario

Sample Request(s)

runtime config:

"runtime": {
    "rest": {
      "enabled": false,
      "path": "/api"
    },
    "graphql": {
      "allow-introspection": true,
      "enabled": false,
      "path": "/graphql"
    }
  }

Both Rest and GraphQL disabled globally

REST

GraphQL

Rest is Enabled, GraphQL disabled

REST

GraphQL

REST is disabled, GraphQL enabled

REST

GraphQL

Both REST andGraphQL enabled

REST

GraphQL

When globally both rest and GraphQL is enabled, but entity option has it disabled.

config

REST

GraphQL