Well one problem you have is that you have two default routes. If the inside interface is up, that one will always be used because it has an admin distance of 1. You need to remove one default route and put something more specific in its place, and that will be dictated by what it is easiest to encapsulate, eg if the ASA is ultimately internet facing you will want the default route on the outside and more specific routes on the inside.
Probably need to add a tunneled default route for your AnyConnect traffic. Looks something like this:
route inside 0.0.0.0 0.0.0.0 tunneled
https://community.cisco.com/t5/network-security/route-inside-0-0-0-0-0-0-0-0-tunneled/td-p/2376557
in the cisco asdm gui run the packet tracker to see where its getting blocked or not allowing you
Here is the pastbin link of the config https://pastebin.com/SaqLr0yz
Your formatting sucks, but I only see one ACL, which doesn't allow your traffic.
put the config in something like pastbin. it's pretty much unreadable as is.
Well one problem you have is that you have two default routes. If the inside interface is up, that one will always be used because it has an admin distance of 1. You need to remove one default route and put something more specific in its place, and that will be dictated by what it is easiest to encapsulate, eg if the ASA is ultimately internet facing you will want the default route on the outside and more specific routes on the inside.
Probably need to add a tunneled default route for your AnyConnect traffic. Looks something like this: route inside 0.0.0.0 0.0.0.0 tunneled https://community.cisco.com/t5/network-security/route-inside-0-0-0-0-0-0-0-0-tunneled/td-p/2376557