Sort out triggering of docs build

[phil-davis]

When one of the docs repos (docs-client-desktop, docs-ocis, docs-server, docs-webui or whatever) changes, the drone merge CI triggers a rebuild of the docs repo. That docs build job does whatever is needed to grab the latest content of all the docs and publish it all.

With recent changes to the drone secrets, the drone_token is no longer available to the various jobs. And so the attempt to trigger a docs build fails.

We need to sort out how this process will be re-engineered.

Note: the trigger code is still in the drone CI code in each repo - that will need to be either changed to "something" or deleted, depending on how the solution to this issue is engineered.

[phil-davis]

@mmattel FYI - need to discuss this all with anyone who might have good ideas about how this can best be engineered now.

[mmattel]

There is an idea from @dragonchaser and @fschade that looks imho promising, but they can explain better than me 😅 Maybe to join in the mornig our ocis zoom so we can discuss.

[dragotin]

is this still hot?