[Browser project monitors] No option for overwriting namespace

[dominiqueclarke]

Monitor namespace by default is the Kibana space the monitor was created in.

For UI monitors, the namespace can be overwritten per the user's specifications in the Add/Edit monitor flow.

However, there is no way to overwrite the namespace for browser project monitors.

We should update the types for the monitor configuration, found here, so that namespace can be added to monitor.use without type errors.

I believe we may need a change on the Kibana side as well to support namespace from browser project monitors. Further investigation is needed.

[paulb-elastic]

Kibana work done in elastic/kibana#150388, this will be end-to-end tested when this Synthetics Agent change is implemented

[vigneshshanmugam]

Should this be under data_stream.namespace instead of top level? Same feature has been asked here - #749

[vigneshshanmugam]

Discussed on slack, namespace fields under Monitor DSL as topelvel is not extensible given we might want to support data_stream.type and data_stream_dataset. Plus, if we start supporting the namespaces for Lightweight monitors which we likely fix it in next iterations, It would create double work on the agent side and create more confusion as they are in different levels.

Blocking this issue off till necessary Kibana changes are done.
/cc @paulb-elastic

[mholttech]

I just came across this and was wondering when this will be implemented since the upstream work in Kibana is done