Not right, i dont see your static route in any table, you only show a bgp route in the inet.0 table.
Using rib groups you have to put the vrf interface in the inet.0 table where you configure your static route.
If not the route dont have the next hop interface reachable. Sure you could see this with a show route hidden table inet.0. Your default route pointing to the next table is not valid for this purpose.
This command will add the interface routes from a VRF or vpn routing-instances, into a rib-group called RIB. And from this RIBrib to the inet.0 table.
set routing-instance VRF routing-options interface-route rib-group inet RIB
set routing-options rib-group RIB import-rib VRF.inet.0 inet.0
On your example, you dont see the static route in the inet.0 table because you import all routes (excluding interfaces) from the vrf table to the inet.0 table, but you have to import the interface routes. You didnt import the next hop or interface from the vrf to the inet.0 table. This is why you cant see the static route.
Also, you have to configure the other way, from the inet.0 table to the vrf table, if you want to test connectivity with ping or anything else. Again with rib-groups.
set routing-options interface-routes rib-group inet INET
set routing-options rib-group INET import-rib inet.0 VRF.inet.0
If you dont want to import all table routes, you will have to apply import policy.
set routing-options rib-group INET import-policy INET-Policy
set routing-options rib-group VRF import-policy VRF-Policy