Darien edit classroom view -- shared component reorganization?

[srallen]

Darien isn't going to want that same classroom edit page design as I2A because it's still hard coded for the I2A uses. I think I was overly ambitious with trying to make some of these components shared between the two. The programs have distinct view and routing needs, so I think we have a few options:

• Darien gets its own edit classroom page design and we determine which to use similar to what I did in Darien classrooms table #74. I never really liked this solution
• Or we completely separate the shared components into I2A components and Darien components. This would result in some repetition, but that's not necessarily a bad thing.
• Or we separate the view components entirely and use HOC container components to inject in the class methods we want to share between the functional view components.
• And/or abstract out shared API calls and methods into the appropriate ducks into async actions managed by jumpstate.