added fee model that belongs to cases, nested route within cases
add case_id index to fees, which will be the index for all subcase models, and changed Fee variable TYPE to FEE_TYPE because of conflicts
added base fees controller
added shared subheader...needs work, will finsih out all models belongs to case before venturing back
fleshing out fees_controller, changed fee model to "has_one" relationship, because a case can only have one fee model, which should fix our duplicate entry worrying
Back to has_many relationship, but the add fee option disappears if there are any fees as see in the cases/show.html.erb