Test file actions for a range of file/folder combinations

• make test scenarios check that a "standard" range of combinations of file names and folder names work. For example:

• "ordinary" names like textfile1.txt (we do this already)

• names with spaces text file 1.txt and test file1 .txt

• names with ASCII special characters like !@#$%^&*()-_[]{}:;,.?=+ etc.

• names with accent, grave, umlaut - typical European character modifiers

• names with "regular" Unicode characters e.g. Nepali/Hindi script

• names with Arabic characters (a right-to-left script)

• names with emojis embedded

• sort out some test infrastructure so that we can "auto-insert" example tables of file/folder names into scenario outlines (rather than having the same list of examples pasted 100's of times through the feature files)

• sort out a way to be able to tag scenarios in the examples, so that we can choose to run only some of them on every PR, but can run all of them when we choose (e.g. in nightly test runs)

• also have combinations of folders and files that test in multiple levels of sub-folders (and that "stress" the total length of a folder/folder/folder.../filename path)

This comes out of discussion in issue #297

Start with the discussion in issue #297 and inspect the existing feature files and scenario outlines that test file actions. Done means covering the listed filename and folder combinations, including nested and long paths, while providing reusable example tables and tags that support selective PR runs and complete nightly runs.