Fixed #176 - Show only active CMS Blocks

[ronak2ram]

Description

Removed only active block checking code.

Fixed Issues (if relevant)

1. Show only active CMS Blocks #176 : Show only active CMS Blocks

Steps to reproduce

1. Checkout to branch 31-cms-page-graphql-support
   Pull request #31 CMS page/block coverage #105
2. Disable some CMS block: MagentoAdmin > Content > Blocks > choose_your_block ->
   Enable Block: NO -> Save
3. Run this GraphQL query:

{
  cmsBlocks (identifiers: ["disabled_cms_block", "enabled_cms_block","not_existed_block"]){
    items{
      title
      identifier
      content
    }
   errors{
      message
   }
  }
}

disabled_cms_block: identifier of the disabled cms_block
enabled_cms_block: identifier of the enabled cms_block

Expected result

1. Get only cms_blocks with status: enabled.

{
  "data": {
    "cmsBlocks": {
      "items": [
        {
          "title": "Enabled Block",
          "identifier": "enabled_block",
          "content": "<p>g</p>"
        }
      ],
      "errors": {
           [
              "message": "The CMS block with the \"disabled_block\" ID is disabled."
           ],
           [
              "message": "The CMS block with the \"not_existed_block\" ID doesn't exist."
           ],
        }
      }
    }
}

Actual result

{
  "errors": [
    {
      "message": "No such entity.",
      "categoerrorsry": "graphql-no-such-entity",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "cmsBlocks"
      ]
    }
  ],
  "data": {
    "cmsBlocks": null
  }
}

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[paliarush]

We do not need to introduce "errors" for specific queries. "errors" functionality is available out of the box. All you need to do is to throw \Magento\Framework\GraphQl\Exception\GraphQlInputException or another exception which implements \GraphQL\Error\ClientAware from your resolver.

[paliarush]

\Magento\Framework\GraphQl\Exception\GraphQlNoSuchEntityException seems to be suitable here. And please note that it should be translatable (use __())