feat(backend): add Program entity

[pbn4]

Pull Request Template

Issue

Addresses #1867

• This change addresses the issue in full
• This change addresses only certain aspects of the issue
• This change is a dependency for another issue
• This change has a dependency from another issue

Description

This change adds Program entity and a relation to Listing (Many to Many) and Jurisdiction (Many to Many).

Listings management frontend must be updated because right now ListingCreateDto and ListingUpdateDto require at least an empty ListingPrograms array. cc: @emilyjablonski @dominikx96 @seanmalbert

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Prototype/POC (not to merge)
• This change is a refactor/addresses technical debt
• This change requires a documentation update
• This change requires a SQL Script

How Can This Be Tested/Reviewed?

Provide instructions so we can review.

Describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have updated the changelog to include a description of my changes
• I have run yarn generate:client if I made backend changes
• I have exported any new pieces in ui-components

[netlify]

✔️ Deploy Preview for dev-storybook-bloom ready!

🔨 Explore the source changes: 634ecf4

🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-storybook-bloom/deploys/61718eb8772aa40007b2d892

😎 Browse the preview: https://deploy-preview-1968--dev-storybook-bloom.netlify.app

[netlify]

❌ Deploy Preview for dev-partners-bloom failed.

🔨 Explore the source changes: 634ecf4

🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-partners-bloom/deploys/61718eb8b02f2200083decd2

[netlify]

✔️ Deploy Preview for dev-bloom ready!

🔨 Explore the source changes: 634ecf4

🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-bloom/deploys/61718eb8a2225800072fe1d1

😎 Browse the preview: https://deploy-preview-1968--dev-bloom.netlify.app

[emilyjablonski]

@seanmalbert Can I get your feedback here? This review has been blocking me on the Program ticket for a bit

[pbn4]

Addresses #2000 too

[seanmalbert]

@pbn4 ,
This looks good, but take a look at my feedback for the preference update PR, particularly in regard to how we're handling pages. Depending on how we handle that, this may need to get updated as well.

[seanmalbert]

@pbn4 ,
From our conversation in stand up yesterday around preferences and pages, @kathyccheng stated that programs like preferences will have their own separate pages and we can use the ordinal for that. And unlike preferences, which has a UI that relies on pages in the meantime, we can safely remove page from listing-program.