change asset path args

[Geokureli]

fixes #2547

AssetPaths has always been a clunky system, whenever people come to me with issues regarding it, I tell them just to delete it and use String paths.

Problems

• Duplicate filenames break down the entire system. even when they are in different directories, or if one of them is excluded via Project.xml
• Custom rename arg only takes the file name, and ignores the directory

Solutions

• Allow duplicate field names, warn the user and omit the duplicated field
• Change filterExtensions to an include/exclude regular expression, allowing exclusion for any context.
• Change custom renaming to take the entire filepath, not just name and extension

[Geokureli]

@player-03

Plus your exclude example should be "/exclude/|\.ogg$".

"\.ogg$" is correct, I'll change "/exclude" is actually preferred since it will skip the directory, where "/exclude/" will recursively scan the directory and exclude all files within it. I'm still thinking about how to explain that. ("/exclude$" would be best but I thought it would be confusing)

The old version, though not very flexible, was easy for new programmers to understand. Jumping straight from there to regular expressions may scare them away.

IMO the old system was practically unusable, it was rare that this tool was actually worthwhile. There's still some stuff I want to try and do to improve this. but even with these changes my gut says to just remove AssetPaths from the templates/demos and reinforce the usage of string paths, which is even easier for new programmers to understand, imo. especially since VSC has "right click->copy relative path"

[Geokureli]

that said, input is absolutely welcome as I'm still not 100% sure what the best solution is. So far this is my best guess

[player-03]

I'd say the best solution is to allow both wildcard strings and regexes. To distinguish, just check if the user wrote "*.gif" or ~/\.gif$/. Yes it's possible; see my pull request.

[Geokureli]

Another thing I was wondering, since include/exclude will always have to match the Project.xml include/excludes, is it possible to auto-apply those filters and only check the files that will actually be exported?

Even if we could, I wonder if there are drawbacks to this. Would it bog down compile time? Is it worth forcing everyone to wrap AssetPaths.some_file__ogg refs in #if desktop blocks?