New test data for importing LIFT with <span>s

Not yet used; next commit will integrate this into PHP unit tests.
Add failing test for importing LIFT with <span>s

Once <span>s are properly handled in LIFT import, the test should start
passing.
Add two more tests for <span>s in LIFT import

This time we're testing importing <note> fields containing, or not
containing, <span> elements.
Add parser for entry-level note fields

Note that this does not yet handle <span>s correctly, but it does handle
notes that contain only text.
Refactor note parsing in LiftImport

There's already a readMultiText function; use it instead of
re-implementing it. DRY.
Deal with <span>s as if they were string values

This is a good first approach to the problem of <span>s found in
multitexts: just pass them through as strings, so that the final lexicon
contents will include values like "foo<span lang="en">bar</span>".
Merge remote-tracking branch 'lf/master' into feature/spanInLiftImport

Conflicts:
	src/models/languageforge/lexicon/LiftDecoder.php
	test/php/languageforge/lexicon/LexTestData.php
	test/php/languageforge/lexicon/LiftImport_Test.php
fix up failing tests
wip: move error reporting up to LiftImport, add error reporting to Example.
Add unit test. Simplified LiftImportNodeError.
all LIFT import tests check for no errors in import report
fix up span import in MultiText to sanitize everything except the span
add node error stack so errors can be handled relative to the current node error
add node errors for multitext sanitize spans
Add error checking to readMultiText. Add multitext identifier to the report.
Merge remote-tracking branch 'lf/master' into feature/spanInLiftImport

Conflicts:
	.gitignore
	src/models/languageforge/lexicon/LiftImport.php
fix failing test
fix up zip import tests to cleanup after themselves; also use absolute assets path (rather than relative)
can import zip as well as LIFT
rename to importProjectZip since file is already uploaded and is now being imported