Docker container doesn't start because of foreign key constraint violations - prevents the README update PR from being merged, so that people will know that this project is deprecated.

[lizmstanley]

I tried pushing code changes to a branch so I could create a PR, but I don't have permissions, so I'll describe the fix here.

Starting up the docker container, we have two issues with the database that cause it to fail (and I assume this is why CI is failing.)

1. In 'testdata.d/08_01_test_data_ebl.sql' there are multiple inserts using the cargo_movement_type 'BB', but there is no 'BB' in cargo_movement_type. I suggest adding BB,Break Bulk,The carrier or its agent or subcontractor has received the cargo which is not containerized. to cargomovementtypes.csv.
2. in testdata.d/segregation_group_code there is an insert into dcsa_im_v3_0.dangerous_goods_segregation_group with a segregation_group_code "1A". There is no "1A" segregation group code. In dgsegregationgroups.csv, it looks like it should be "1". I suggest changing the insert to 1.

Hopefully this will help get the IM repo deprecation README update PR merged, so that it's clear we should not be using the information in this repo, such as facility type codes, etc.