Doc: Resource type updates-Import from Git & deploy image

Scope

• Required updates are described in this recording--> skip to 18:33 minute mark in the video to find a description of what changes with this epic and description of doc changes. 
• Only small updates required. Here are some options for doc updates::
  • This change in the UI involves moving the Resources section in git flow for importing code to the Advanced options section the UI  to make it less visible to users since users will be able to set a default resource type in User Preferences when 4.12 release (refer to epic ODC-6683 (RHDEVDOCS-4236). I am not sure if users will be overriding the default selection in User Preferences or just updating the default selection from this Advanced options area when importing from git (check with engineering). This move of Resources area affects the Creating applications using the Developer Perspective topic in the documentation. In this topic. step 7 needs to be removed or tweaked a little in the Upload JAR files for easy deployment of Java applications.  In the 4.11 doc, step 7 reads as "In the Resources field, choose the resource type for your application." In 4.12, this step was modified already per 4.12 epic ODC-6683 (RHDEVDOCS-4236). 
    • If this step is removed, you must think about the note that was added for epic ODC-6683 (RHDEVDOCS-4236) that also contains info that the Serverless Deployment option is only available if installed on the  cluster with serverless installed and perhaps add that blurb to the Adding User Preferences topic Check out this PR from doc updates from RHDEVDOCS-4236. 
    • If this step is kept (probably the easiest option since work was done for previous epic), the wording behind step 7 should change in the Creating applications using the Developer Perspective|https://docs.openshift.com/container-platform/4.11/applications/creating_applications/odc-creating-applications-using-developer-perspective.html#odc-creating-applications-using-developer-perspective] topic to let users know they can set default resource type values in Adding user preferences topic and if desired, the user can update the resource type settings from the Advanced options view when importing from git.