Endpoints for Listing Details Page, Middleware, Cache Service, SQL Query Logging Configuration

[Prakhar896]

Overview:

• /listingDetails endpoint for frontend to fetch listing data.
• /getListingImage/:name endpoint for frontend Image components to fetch listing images.
• /uploadListingImage endpoint for frontend to submit and attach new images to food listings.
• /updateListing endpoint for frontend to update listing data.
• Cache service created in services/Cache.js that is a key-value persistence storage option for minimal persistence needs
• storeFile Multer middleware that stores files into FileStore directory
• logRoutes middleware that logs all endpoint requests

Debug Makeshift Measures:

• On boot, there's a onDBSynchronise method in which the code will auto-generate a sample FoodListing for my listing endpoints to work with (note that sample listing requires existence of sample3.jpg named file in FileManager context)
• If there's any existing FoodListing, it'll latch onto that instead

Sensitive changes:

• Commented out all the associations and made guestID primary key of Guest model for now. This is because there's some issues with the relationship design that are causing problems when creating instances of the models.

WILL NEED to be fixed later.

[Prakhar896]

Skipping this middleware's implementation for now. We can always impose the headers requirements later. Speeds up debugging/development.