1577/download button can show and be non functional

[KrissDrawing]

Pull Request Template

Issue Overview

This PR addresses #1577

• [x] 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

It will hide download button, when application is present but nothing to download. We we're hiding apply sections based on application methods presence, so now i got to create some more conditions, as that one is not accurate anymore.

How Can This Be Tested/Reviewed?

edit application process in partners to have Is there a paper application? set to yes, but leave text field below empty. It shouldn't change way the listing on public site is displayed (it won't render download button). Test with other combinations from Application Types and Application Address as it's all connected.

Checklist:

• [x] My code follows the style guidelines of this project
• [ ] I have added QA notes to the issue with applicable URLs
• [ ] 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 run yarn generate:client and/or created a migration if I made backend changes that require them
• [ ] I have exported any new pieces added to ui-components
• [ ] My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
• [ ] Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

• Read and understand the issue, and ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
• Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

[netlify[bot]]

✅ Deploy Preview for detroit-partners-dev ready!

Name	Link
🔨 Latest commit	a0674e93c0323e3d44f4938f9d1029b13dc3028a
🔍 Latest deploy log	https://app.netlify.com/sites/detroit-partners-dev/deploys/6450d33d95824d0008d8ba6a
😎 Deploy Preview	https://deploy-preview-1621--detroit-partners-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify[bot]]

✅ Deploy Preview for detroit-public-dev ready!

Name	Link
🔨 Latest commit	a0674e93c0323e3d44f4938f9d1029b13dc3028a
🔍 Latest deploy log	https://app.netlify.com/sites/detroit-public-dev/deploys/6450d33df4008c0008d5cd24
😎 Deploy Preview	https://deploy-preview-1621--detroit-public-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.