1. In the lines:
[code:1]static (inside,outside) 184.108.40.206 192.168.x.10 netmask 255.255.255.255
route outside 0.0.0.0 0.0.0.0 220.127.116.11 1[/code:1]
IP addresses 18.104.22.168 and 22.214.171.124 are not in the 126.96.36.199/29 range. Assuming that 188.8.131.52/29 is correct, the range is from 184.108.40.206 to 220.127.116.11. Use any IP in this range except of-course 18.104.22.168 which is your vlan2 interface's. I know these are not your real IPs, but I'm saying just in case you have the same problem.
2. Upto this point, I see no reason why it shouldn't work, still the config is not very safe. For example, the lines:
[code:1]access-list ACLOUT extended permit ip any any
access-list ACLOUT extended permit icmp any any
access-list ACLOUT extended permit tcp any any [/code:1]
It's allowing all traffic from outside to go in. It's better to allow only your servers and configure NAT. NAT lets replies from the outside to enter in without an allowing ACL at the outside.
To configure NAT:
[code:1]nat (inside) 1 192.168.x.0 255.255.255.0
global (outside) 1 interface[/code:1]
And to allow your inside servers to be reachable from outside, add some thing like this:
[code:1]access-list ACLOUT extended permit tcp any 70.80.36.x eq 80[/code:1]
Here I'm assuming you have a web server, hence port 80. Change it to the specific port you use on your server. Sure you can add icmp too for ping to work.
3. I don't see the need for ACLIN. The ASA by default allows traffic to flow from a higher security interface (inside) to a lower security interface (outside) unless another ACL denies it. Try removing the line access-group ACLIN in interface inside and you'll probably see that it still works.
4. No you don't need to set the interfaces to the same security levels.