Add city council mtg zoom link URL

[jerrycyip]

📜 Description

• Describe the general shape of this PR (new feature? refactor? bug fix? one-line change?)

  • Per business owner clarifications from Ellina Yin, added a configurable constant to use as the default zoom url link for city council meetings: 'https://sanjoseca.zoom.us/j/88471470054'. Prior to changes, there was no meeting zoom url link to redirect users and the application simply opened another tab with the same ATM application page.

• Describe what changes are being made

  • Per business owner clarifications from Elina Yin, added a configurable constant to use as the default zoom url link for city council meetings: 'https://sanjoseca.zoom.us/j/88471470054'.
  • As part of the changes also removed the button element tag which was originally inside of the zoom url anchor tag as this is poor practice from a non-semantic HTML perspective and is likewise not good for accessibility (A11) purposes. To retain the same design, I instead applied the button styling to the zoom anchor tag itself. In addition, I fixed the anchor tag's styling such that the clickable area of the anchor tag only extends up to the width of the element instead of the entire width of the container (see short video below for demo of before/after).

• Describe why these changes are being made

  • See above

• List the use cases and edge cases relevant to this PR

  • See above

• Describe how errors will be handled. How will we know if this code breaks in production

  • N/A

• Describe any external libraries/dependencies added or removed in this PR

  • N/A

• Describe any security risks are there regarding this change

  • N/A

• Describe how you tested these changes

  • Tested before and after changes in front-end browser.

• Link to relevant external documentation

  • latest changes are per latest MPV designs

---

📋 Mandatory Checklist

• Example of a checked item (please remove when creating your Pull Request)

• Linked to the Github Issues being addressed using the right sidebar ➡️

• Have you discussed these changes with the project leader(s)?

• Do all variable and function names communicate what they do?

• Were all the changes commented and / or documented?

• Is the PR the right size? (If the PR is too large to review, it might be good to break it up into multiple PRs.)

• Does all work in progress, temporary, or debugger code have a TODO comment with links to Github issues?

• If you changed the user interface, did you add before and after screenshots to below?

---

🖼️ Screenshots and Screen Recordings

Before

pre_change_behavior.mov

After

post_change_behavior.mov

---

📘 Glossary

• PR = Pull Request

[JMStudiosJoe]

Updating to env car would be best if possible at this time, if not let me know in response to comment here please.

[JMStudiosJoe]

Let's add to the env vars that way easier to update if needed

[jerrycyip]

Appreciate the review and suggestion! Accordingly, I've moved this to an environment variable as per latest commit: "1fca7278601741cf38ad9f51d6e959845d21d9bb". It took some trial and error before I remembered that create-react-app requires environment variables must have the prefix "REACT_APP_" so I also added a comment in the environment file as a reminder.
(side note: I also merged in the recently approved PR 350 into this branch as part of latest commits)