Hello junosuser33,
the above topology is the standard BGP multihoming topology. From a carrier you get a cable with a standard /30 or even a /31 subnet configured onto which the BGP session is configured.
On the LAN side of your Routers (R1 and R2) you can configure VRRP or OSPF. I'd recommend you to connect the two Routers directly as well and configure iBGP on it, in case the uplink of Carrier 1 fails and the VRRP master is not switching to R2.
The below topology is quite uncommon, and it introduces an additional failure point. E.g. if you are facing packet loss to the Carrier, is there any issue on the carrier side or on your Aggr. SW? Additionally, BGP sessions to VRRP VIPs are not a good way, in this case it would be better to establish BGP session to the physical interface address. The prerequisite for this is of course, that the carrier provides you a /29 prefix at minimum, which is mostly not the case.
To have so many BGP sessions intoduces other issues, like BGP dampening issues. E.g. if R1 crashes, two BGP sessions would go down which could trigger BGP dampening in other ASNs.
So I'd suggest keep it simple, and connect to the Carriers with a dedicated cable. It makes your life much easier and a 1+1 redundancy should be enough for an Enterprise environment.