drop corresponding records from metadataStatus when deleting a metadata

[landryb]

geOrchestra/geonetwork checklist
cf geonetwork/core-geonetwork#8693

it might also be needed on 4.4, dont have an instance to test, but to check one can do

select * from metadatastatus where metadataid not in (select id from metadata);

if there's some records, then that's leftovers from deleted metadatas.

• PR only involves cherry-picked commits from upstream.
• PR contains custom code which will soon be available in an upstream release and can be overriden => mention core-geonetwork version if possible.
• PR contains custom geOrchestra code, which need to be verified during future migrations.
  • I have properly filled the migration-dev-guide.md file.

[pmauduit]

not that much to review here, missing a bit the context, but reading the upstream issue, that looks fine.

I don't get why all this is not managed by the JPA shenanigans, I'd have expected that as long as we have dependencies defined in the (Java) object model, then removing a md would also cleanup underlying objects, but as long as the other objects are removed by hand 2 lines above the modification, fine then.

[landryb]

thanks ! i guess i'll have to forward-port it to #321 ? since it hasnt been merged upstream yet..