Import: Add DataFlow descriptions to importer classes, with tests, for making visible in UI #2511
Who is this PR for?
What problem does this PR fix?
The log of import tasks is somewhat visible, but it's more intended for developers. There's no way for district project leads to see importers directly, particularly for other kinds of imports that are semi-automated, or from different sources other than regular SIS syncs.
What does this PR do?
Adds some minimal description in code of what these are, intended to be put in a UI for users, alongside other kinds of data flows not yet visible (eg, student voice, reading data, transitions).
I'm mot sure doing this in code over docs adds real value, but trying it out for now.
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?