Fixed DB seeder to truncate the asset_maintenances table
Fixed DB seeder to truncate the asset_maintenances table

This wouldn’t have affected anything in production, but could cause some weird behavior if re-seeding often, since the suppliers table gets stomped on but the old maintenances remained, leaving ghost entries and associating the wrong (old, now defunct) supplier with the maintenance as new supplier IDs get generated.

mtucker6784/snipe-it,uberbrady/snipe-it,uberbrady/snipe-it,snipe/snipe-it,uberbrady/snipe-it,uberbrady/snipe-it,snipe/snipe-it,mtucker6784/snipe-it,snipe/snipe-it,snipe/snipe-it,mtucker6784/snipe-it,mtucker6784/snipe-it,uberbrady/snipe-it,mtucker6784/snipe-it