Resolves #4686 add another bank to seed

[Benjamin-Couey]

Resolves #4685

Description

This PR modifies the db/seeds.rb file to add another diaper bank with a partner and other associated records. CONTRIBUTING.md was also updated to include the login information for the new diaper bank and partner.

In total, the following records were added to the seed:

• The new Organization Second City Essentials Bank
• Four items unique to the new bank, each based on a random BaseItem, named "Second City Item 1"
• New Users for the new bank, "[email protected]" and "[email protected]"
• 20 Donations and Distributions for the new bank
• 25 Purchases for the new bank
• DonationSites for the new bank, based on the city and state of the bank.
• Two StorageLocations for the new bank.
• Request Units, ProductDrives, ProductDriveParticipants, Manufacturers, and 'Vendor's for the new bank.
• The new Partner "Second City Senior Center"
• Several Requests made by the new partner to the new bank (this was handled by exiting Partner seeding code).

The seed uses both hand-written values and the Faker library to populate addresses, emails, etc. When creating entirely new records, I favored Faker for the sake of better looking demos but didn't update existing hand-written values.

For most of the records associated with an Organization, the seed only created records for the Pawnee Diaper Bank. I updated these sections to only create records for the new bank and not the existing SF Diaper Bank as they was not requested by the issue. I tried to modify the code so that it would be easy to define a list of banks for which these records should be created.

Type of change

• New feature
• Documentation update

How Has This Been Tested?

As far as I could tell, there were no automated tests associated with the seed and so relied on manual verification. I verified that rake db:reset runs without issues with the modified seed and manually verified that the database contained the new records associated with the new bank.

I created a unit test for a utility function added to Organization.

[cielf]

Hey @Benjamin-Couey - I'm liking what I'm seeing from a functional pov. With the second city items, I have one question, though.

Are we guaranteed to have at least one each of donation, purchase, distribution, and request among those 4 items?

My concern is false positives when we are using them for manual testing -- that, with these extra items, we would rely on there being instances with them, and if there aren't, we might assume that everything is fine.

[Benjamin-Couey]

@cielf There is currently no guarantee that the second city items will be used for the donations, purchases, distributions, and requests.

I can work on explicitly adding examples of those records using the second city items.

[cielf]

(Nods) Yes please.
I haven't checked, but could you also make sure at least one of them has an inventory level that is less than its recommended quantity?