The default checked publishing option "Published" does not apply for content types with a workflow that has a moderation state != published as default

Problem/Motivation

If you create a content type admin/structure/types/add, per default the Published and Create new revision checkboxes are being checked within the vertical tab Publishing options. The problem is, if the content moderation module is being installed, and the created content type is being added in the "This workflow applies to" section of a workflow with a default moderation state set to for example Draft, as long as the state != Published, when a node is getting created that node isnt set as Published as set on the content type, but after submission its publishing state is unpublished with a moderation state of draft. So the default option published has no effect nor purpose with the content moderation module installed and is rather contradictory compared to the expected outcome.

Steps to reproduce

• Create a content type admin/structure/types/add called "Playground", and keep the default settings "Published" and "Create a new revision" for the "default publishing options".
• Add the Playground content type to the list of content types the "default editorial workflow" applies to on admin/config/workflow/workflows/manage/editorial?destination=/admin/config/workflow/workflows
• Compare admin/structure/types/manage/playground and node/add/playground

Proposed resolution

Drop the Published checkbox on the Publishing options vertical tab on the Edit local task for a content type when the content moderation module is installed.

The only question, it might be useful to make the setting for the "default moderation state" available on the content type as well. So you have the select element for a workflow on the workflow as well as the content type it applies to. Only downside and tricky detail. If you provide that ability and you have a workflow that is enabled for content type A, B and C and one user changed the "default moderation state" on content type B, that change would automatically apply to content type A and C as well or should it be possible to alter the available content types individually? The former would need a clear labeling, while the latter would require a select element for each workflow a content type is added to.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet