I was thinking how to do it, at the moment there is a native Vlan mismatch between the Catalyst and the MS, thats why I was hoping if you changed the management Vlan, that would also change the native Vlan.
Anyway it looks like a way round this would be to have a second link between the catalyst and the MS, with the native vlan set to 25 at both ends, then change the management vlan to 25, it should then start communicating to the Meraki cloud through this second link and we can disconnect the original link.
think of the mgmt int/IP on the meraki switch like just a client/host IP that needs to talk to dashboard. as long as the vlan is allowed on the uplink port(s) and not blocked by any upstream firewalls it should reach dashboard.
the native vlan/allowed vlans/port mode all need to follow standard switch config principles. meaning if the uplink is a trunk (most likely) it needs to be a trunk on the other end. and the native and allowed vlans should match.
again, in the world of meraki switches the mgmt vlan is a little different from what folks are used to with traditional switches.