Graylog REST API is inconsistent for 'id' field creating from endpoint

The Graylog REST API is inconsistent with regard to "id" field (Stream and Outputs).

## What?

It should be possible to give an ID value while creating all REST resources which will then be used in all following requests/responses. Rules and Pipelines are like this at the moment, but Stream and Outputs are not.


## Why?

We would like to use external configuration management (like ansible or puppet) to fully manage our configuration in Graylog, this requires to be able to set the initial id for all resources via the external tool. This allows a homogenous environment regarding IDs over different Graylog clusters (in our env 7 Clusters). Currently, two streams (same named, and should behave the same) in two environments are currently having different ids, as we can not set them while creating the resource.

Be able to use external configuration management tools which can fully handle the Graylog configuration from initial creation over updates to deletes if the resources are not needed anymore (decommission).

## Your Environment

* Graylog Version: 4.2.7
* Elasticsearch Version: 7.10
* MongoDB Version: 4.4
* Operating System:
* Browser version:
* Context: HS#836730717