Drone Series - Service Request

Goal of this challenge is to have package request and request details backend and frontend integrated. Also, a few api changes are required.

Backend api changes
    1.Package request will contain fields based on service type. For now, we need to support just 2 types (imagery and delivery) but the solution needs to be flexible for extending this list.
        Imagery request will contain these fields:
            request description
            regions of interest (the user will mark these on the map). These are already described by the Mission.ZoneSchema model so move it from Mission model to PackageRequest

        Delivery request will contain these fields:
            starting point
            destination point
            launch date
            contact info (recipient name and phone number)
            item desctiption
            item weight
    2. Remove Provider.category attribute and add category attribute to Service model
Make sure to update the necessary service methods and swagger documentation too.

With the above backend changes, wire these frontend pages to the backend api
    1. /service-request
        this page neds to be aware of the service type and display the fields in the left form accordingly. 
    2. /my-request-status
        This one should be straightforward with a call to /requests
    3. /status-detail
        Data for this page is available in Mission model (can be fetched from package request)


Base code for this contest is in the packageRequest branch in both dsp-server and dsp-frontend repositories

https://github.com/topcoderinc/dsp-frontend
https://github.com/topcoderinc/dsp-server

Final Submission Guidelines

Submit a git patch for your changes to the base code
Submit a short video demonstrating the implemented features
Submit updated deployment guide
Submit a short verification guide with screenshots (verification guide should be placed in the /verification-docs directory)