feat: data collection for search

[JasonChong96]

Problem

Before link search can be fully implemented, further collection of data from link owners is required.

#181

Solution

This PR implements phase 0 of the implementation for link search. UI Fields and database columns are added for contact information and description for each link.

Improvements:

• Updated URL drawer margins to fit the design more
• Use of negative margins in DrawerTextField have been replaced by having helper text in absolute position. The negative margins made it hard to debug element positioning in browser debuggers and calculations of margins needed for subsequent elements were also confusing.

Before & After Screenshots

AFTER:
Desktop
Mobile

Deploy Notes

The new migration script should be run before deployment. The new columns will be nullable and compatible with both the new and old code.

TODO:

• Create sql migration file
• Update url retrieval endpoint to return new fields
• Add new fields in edit url UI (Desktop)
• Add new fields in edit url UI (Mobile)
• Update call to url edit API
• Update url edit endpoint
• Add validation for contact email

[liangyuanruo]

isn't there an inconsistency, if the default value populated by the SQL migration is an empty string, but here we are insisting on allowNull: false and isEmail: true?

would it be easier to simply allow null values?

[liangyuanruo]

it's dangerous to backfill empty strings in the DB, yet insist on non-nullable email validation in the ORM.

[liangyuanruo]

lgtm