In general terms, @pcunite prepared a really good tutorial on how to do VLANs properly … it includes example of switch configuration. Another good tutorial by @sindy explains different bridge personalities.
In short: bridge is a “switch-like” entity and a port (of the switch-like entity). Whatever you do with bridge port, specially with regards to VLANs, you have to configure it explicitly, just the way you do for other bridge ports. Default (all over ROS) config is to have all bridge ports configured with PVID=1 (which makes using VID 1 explicitly somehow dangerous as one has to be very careful to configure things correctly). In your case you should be able to set management IP address to bridge port directly as it’s (by default, implicitly) set as access port with PVID=1.
Another general lesson: as soon as physical port becomes part of bridge, you should not configure any L3 stuff on it … you have to use bridge port for that. ROS doesn’t block it but it’s wrong anyway. At the same time you have to add bridge port to appropriate interface list (basic distinction between interface and port is that port is L2 entity while interface is L3 entity - based on L2 entity and assumes same name).
BTW, the admin-mac property of bridge is invalid, it should be colon-separated octets but first field in your config is word-sized (dea … should be de).