Default to published on certain entity types

Problem/Motivation

When cloning it is possible to also publish the cloned entity, but there are some situations where it is preferred to force them as published to prevent mistakes.

For example when cloning custom blocks (from block_content), if the published box is not checked, they go into an unpublished state and cannot be published (there is no form element for custom block publish).

As a workaround the form could just be modified with a form_alter.

(There is a core issue that will allow custom blocks to be published: #2834546)

Steps to reproduce

1. Create a custom block, clone it and leave it unpublished
2. Add the block to something like layout builder
3. View as anonymous, block is not visible

Proposed resolution

Allow configuration of default published status on a per-entity (?) level.

Remaining tasks

User interface changes

API changes

Data model changes