Hi, Egert
In Junos an Aggregated-Ethernet (ae) interface is the same thing as a port-channel in Cisco. An ae interface is just a bundle of physical interfaces; this bundle can be a group of L2 (family ethernet-switching) or L3 (family inet) interfaces. As you mentioned, ethernet-switching is not supported in high end SRX, however you can configure a L3 interface with sub-interfaces that will understand vlan-tagging.
Based on the provided configuration I can see that you have two L3 interfaces (one with vlan-tagging) acting as VRRP gateways and you mentioned that you dont have a chassis cluster. The steps you will need to follow are:
1. Enable, at least, 1 ae interaface:
user@host# set chassis aggregated-devices ethernet device-count 1
Ref: https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/device-count-edit-chassis.html
2. Create an ae interface (ae0) by bundling ge-0/0/0 and ge-0/0/2:
user@host# set interfaces ge-0/0/0 gigether-options 802.3ad ae0
user@host# set interfaces ge-0/0/2 gigether-options 802.3ad ae0
Ref: https://www.juniper.net/documentation/en_US/junos/topics/topic-map/security-interface-config-aggregated-ethernet.html#id-deleting-aggregated-ethernet-interface
3. Configure ae0 with subinterfaces using vlan-tagging (Router-on-a-stick):
user@host# set interfaces ae0 vlan-tagging
user@host# set interfaces ae0 unit 202 vlan-id 202
user@host# set interfaces ae0 unit 202 family inet address 192.168.3.254/24 vrrp-group 1 virtual-address 192.168.3.1 priority 200
user@host# set interfaces ae0 unit 202 family inet address 192.168.3.254/24 vrrp-group 1 accept-data authentication-type md5 authentication-key [password]
user@host# set interfaces ae0 unit 205 vlan-id 205
user@host# set interfaces ae0 unit 205 family inet address 192.168.1.4/29 vrrp-group 2 virtual-address 192.168.1.2 priority 200
user@host# set interfaces ae0 unit 205 family inet address 192.168.3.254/24 vrrp-group 1 accept-data authentication-type md5 authentication-key [password]
Follow the same format to configure other sub-units and note they have to have their own vlan-ids.
With above configuration you just need to make sure that your switch also has a L2 port-channel created acting as a trunk port and passing the vlan-ids created on the sun-units (202 and 205).
Remember that ge-0/0/0 and ge-0/0/2 are currently part of a security-zone; you will need to include ae0.202 and ae0.205 within those security-zones as well.
I really hope this was the information you were looking for. Please mark my comment as "Solution" if it applies.