feat: Support PDF uploads or webpage links for building selection criteria

[jaredcwhite]

Issue

Addresses #1755

• 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

For listings management, this PR add the ability to specify either (a) a PDF upload, or (b) a link to an external webpage with information for building selection criteria.

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/address technical debt
• This change requires a documentation update
• This change requires a SQL Script

How Can This Be Tested/Reviewed?

Look under the Additional Eligibility Rules section when adding/editing a listing.

• Desktop View
• Mobile View

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

[netlify]

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

🔨 Explore the source changes: 6689db5

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

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

[netlify]

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

🔨 Explore the source changes: 6689db5

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

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

[netlify]

❌ Deploy Preview for dev-bloom failed.

🔨 Explore the source changes: 6689db5

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

[jaredcwhite]

@slowbot I'd like to get your take on how I worded the external webpage vs. PDF upload nomenclature. I think there was some prior confusion over whether an external URL would link to a PDF hosted elsewhere vs. an actual website, so I tried to word things to make it clear PDFs should always be uploaded. Let me know what you think!
https://deploy-preview-1893--dev-partners-bloom.netlify.app/listings/add

[slowbot]

1. Uploading file does not persist after save as draft
   
   
2. Can we use the table view here rather than printing the url?
   
   

[jaredcwhite]

@slowbot All right I implemented the table (request 2). As far the issue of the data disappearing, I wasn't able to recreate that. If you're still seeing the issue, I'll try to investigate further.

[slowbot]

@jaredcwhite I'm still seeing the issue on the deploy branch but that may be outdated. Do you have an updated deploy branch I can use to test?

[seanmalbert]

@jaredcwhite I'm still seeing the issue on the deploy branch but that may be outdated. Do you have an updated deploy branch I can use to test?

@jaredcwhite and @slowbot, the deploy branch won't have the database changes required for this to save properly, since those still point to the dev db. Since @pbn4 approved the backend and if it looks good visually, then we can merge this and have it QAd on dev. Sound good?