Where should we add the ca editor config page in order to work for /config/global folder?
theoretically it is possible by
adding a content folder e.g. /content/global with a property sling:configRef pointing to /conf/global
adding a CA config editor page below /content/global
but in practice this does not work as currently the sling caconfig implementation has a special treatment of fallback paths like /conf/global and does not allow persisting configuration to them using the caconfig management API (on which the CA config editor relies):