Assuming that the aruba switch is properly configured.
/interface bridge
add name=bridge-all vlan-filtering=yes
/interface vlan
add interface=bridge-all name=vlan100-LAN vlan-id=100
add interface=bridge-all name=vlan101-WIFI vlan-id=101
add interface=bridge-all name=vlan199-ADMIN vlan-id=199
/interface bridge port
add bridge=bridge-all interface=ether2 pvid=100 frame-types=admit-only-untagged-and-priority-tagged
add bridge=bridge-all interface=ether3 pvid=100 frame-types=admit-only-untagged-and-priority-tagged
add bridge=bridge-all interface=ether4 pvid=100 frame-types=admit-only-untagged-and-priority-tagged
add bridge=bridge-all interface=ether5 pvid=199 frame-types=admit-only-untagged-and-priority-tagged
add bridge=bridge-all interface=ether6 pvid=199 frame-types=admit-only-untagged-and-priority-tagged
add bridge=bridge-all interface=ether7 pvid=199 frame-types=admit-only-untagged-and-priority-tagged
add bridge=bridge-all interface=ether8 frame-types=admit-only-vlan-tagged
/interface bridge vlan
add bridge=bridge-all tagged=bridge-all,ether8 vlan-ids=100
add bridge=bridge-all tagged=bridge-all,ether8 vlan-ids=199
add bridge=bridge-all tagged=bridge-all,ether8 vlan-ids=101
I only address here the vlan part. The problem with your config was that you did not include the bridge itself as a tagged "port".
Because you are "tapping" into the individual vlans, the bridge(cpu from the switch logic) is also a virtual port that needs to "pass" tagged traffic
Other considerations:
Having vlan-filtering=no on the bridge defeats the purpose of using vlans as the defined rules are not enforced.
Different things happen on different devices(because of the different switching chips used).
After testing if things work you should enforce the settings by also enabling "ingress-filtering=yes" on each port in the bridge (in "/interface bridge port")