[CORL-1040] Story Update Fix

[wyattjoh]

What does this PR do?

It turns out, when some queries are formatted in a particular way, graphql will create javascript Object's with Object.create(null) (ref: graphql/graphql-js#504) even though this practice is discouraged (ref: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/create).

This causes issues when you try to call prototype builtin's like hasOwnProperty on objects created this way.

This PR adjusts the linting rule for the no-prototype-builtins rule to prevent us from using these builtins to prevent this from causing issues in the future.

What changes to the GraphQL/Database Schema does this PR introduce?

None.

How do I test this PR?

Previously, the following GraphQL mutation would return an error:

mutation ($id: ID!, $url: String) {
  updateStory(input: {id: $id, story: {url: $url}, clientMutationId: ""}) {
    story {
      id
      url
    }
  }
}

Now, it does not. The is because the object created in {url: $url} is via Object.create(null). Now that we no longer use prototype builtin's, we don't encounter this bug.