include_tasks files that in turn contain import_tasks cause cryptic errors

It appears to be good practice to avoid using import_tasks in a file if the file itself was included with include_tasks.

Because if you don't, expect to get cryptic error messages like:

# ERROR! Unexpected Exception, this is probably a bug: expected str, bytes or os.PathLike object, not NoneType