In general there is no support in JSON Schema to refer to other instance values. In this simple example you could express what you want in JSON Schema by modeling only the valid options, i.e. a oneOf wrapping both your properties and only allowing valid combinations, e.g.
However the UI for this will by default not be nice to use as our support for generic oneOf only comes with a generic basic UI. So for a good usability you would then need to create a custom renderer for this.
If you are not required to express your valid selections via JSON Schema but are fine with coding them into the UI then you can just create a custom renderer for the second property of your original schema. This custom renderer can just reuse our existing oneOfEnum renderer but filter the options accordingly to the current selection in the other control.
Unrelated to the issue at hand, but you probably don’t want to place the title property into the const but rather outside of it.