do the ORG filtering as part of the mongo query. Also, don't trigger met...

...adata inheritence calculations when just trying to load 'about' information, which is not tied into the course tree anyhow (i.e. no parent/child relationship)

Some code cleanup regarding eligibility to apply inherited metadata

forgot to return result
You can leave as is for now, but I think a better filtering model would just be by native field name - key value pairs: so; 'org', 'course', 'start', 'display_name'. This came up in another thread yesterday w/ @jimabramson and is how I impl'd `get_items` which not only takes arbitrary fields but also lists of values, functions to apply to determine match, regex's, etc. Far more than needed for this PR tho. The `tl;dr;` takeaway is perhaps to just name the arg `org`.