Update shiboken includes to fix Windows build.

[acolwell]

Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. Additionally, make sure you've done all of these things:

• I've followed the contributing guidelines to the best of my understanding
• I've read and understood the contributing guidelines
• I've formatted my code according to Natron's code style
• I've searched the pull requests tracker to ensure that this PR is not a duplicate

PR Description

What type of PR is this? (Check one of the boxes below)

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (non-breaking change which does not add functionality nor fixes a bug but improves Natron in some way)
• Breaking change (fix or feature that would cause existing functionality to change)
• My change requires a change to the documentation
  • I have updated the documentation accordingly

What does this pull request do?

Pyside2 and a few other python related packages were updated on MSYS2 in the last week or so which caused the Windows Installer builds to start failing. This change modifies how include paths are specified on the command-line. It appears that shiboken no longer handles colon separated path lists so each include is now specified with its own -I option.

Have you tested your changes (if applicable)? If so, how?

Yes. I verified that these changes fix the installer build locally and via the GitHub action (https://github.com/acolwell/Natron/actions/runs/7514747615)

[devernay]

Does that fail because one or more of the path components contain spaces? In which case double quotes around the variable expansion in the shiboken2 call could also fix it

[acolwell]

Does that fail because one or more of the path components contain spaces? In which case double quotes around the variable expansion in the shiboken2 call could also fix it

It fails because shiboken2 uses a different token to separate paths. On Linux (and I suspect Mac) it uses ':' and on Windows it uses ';'. You can see this by looking at the 'shiboken2 --help' text.

I've also just updated the typesystem path args since the help text reports the same platform difference. I'm not sure why ':' seemed to still work for that argument, but I figure changing it now should help avoid future breakages if they ever change that behavior.