Migration failing on staging

[joepio]

Latest develop failing on staging server:

atomic_lib::db::migrations: Migrating resources from v1 to v2, this may take a while...
thread 'main' panicked at lib/src/db/v1_types.rs:87:51:
ResourceV1 is not supported

This panic happens because a full, namedSubResource is parsed. The migration didn't cover this case. In defense of @Polleps, I find it hard to come up with a situation where a named subresource exists.

I think we should change the behavior: replace both panics with a trace::warn and convert to Subject.

[joepio]

Tested the fix locally. But for some reason the migration didn't log anything in staging, but the new server is running properly and the data is still there. Consider me confused.