ROBOT template based obsoletion

[matentzn]

close #3596 #3594 #3172 #324 #324 #324 #324 #324 #3573 #324 #3570 #324 #3575 #3570 #324 #3442

[nicolevasilevsky]

I can't open the file in Protege.
I think this needs to be:
property_value: IAO:0000231 "out of scope" xsd:string

[matentzn]

There is a problem here with robot remove.. I can either tell it to fix the class hierarchy (i.e if A sub B sub C, you delete B, then add A sub C) or I can tell it not to do it (which means A becomes a floater and needs to be classified manually. The problem is, if I tell it to fix the class hierarchy, it will fix all of it. Which means it will try to fix a million subclass relations that we did not tell it to :( Shit

[nicolevasilevsky]

Oh dear.
It's not the end of the world if this workflow doesn't work out, I can always obsolete these classes one at a time.

[matentzn]

@nicolevasilevsky Put one more time on our agenda, have an idea how to fix this with SPARQL

[nicolevasilevsky]

to do:
check in protege
once passes, merge
after
create new PR with this command
sh run.sh make make related_to_exact_where_label

[nicolevasilevsky]

@matentzn

These terms were missing owl:depracated true. I fixed it manually.

Some terms were left orphaned because the terms that were obsoleted were children of 'disease or disorder'. I added parents to those terms. This won't happen very often.