Include support for Palo Alto Globalprotect split-tunneling includes

Hello,

I think globalprotect offers split-tunneling include configuration, which is ignored in the current release.

```
Unknown GlobalProtect config tag :
*.database.windows.net:1433
*.azure.com:443
*.windows.net:1433

Unknown GlobalProtect config tag : yes
```

It seems to me that this bit of configuration is pretty straight-forward/obvious to reverse engineer. Given some guidance I could also try and help with the implementation.

Best regards,
Vasil

Start by reproducing the reported GlobalProtect configuration parsing with the include-split-tunneling-domain values shown in the issue, then trace how unknown configuration tags are handled. The issue names no files or tests; done means the include configuration is recognized and applied without the reported unknown-tag warning.

Written by the indexing model from the issue text.