Fod On Demand Dynamic Scan Post Build - DAST Automated Scan Support

[pvivekdev]

Support for DAST Automated Scan from Fortify On Demand Plugin (Free Style Template). https://almoctane-ams.saas.microfocus.com/ui/entity-navigation?p=112082/7001&entityType=work_item&id=888034 https://almoctane-ams.saas.microfocus.com/ui/entity-navigation?p=112082/7001&entityType=work_item&id=993003

Added Fod On Demand Dynamic Scan Post build plugin, Added Support DAST Scan types (Website, Workflow Driven). Included Scope settings, Scan Type specific settings, Support to Create Application & Release for DAST. Included Network Auth/ Login Macro Setting to support Website/Workflow Driven. Included HTML File Type control to upload file into FOD API.

Testing done

1. Selection of Application and Release associated with current user.
2. On selection of Fod On Demand Dynamic Post build action loads DAST UI controls.
3. On selection of Scan type - Scan type specific UI controls are loaded.
4. Saving the specific scan settings into DAST Fod API.
5. Loading the saved scan settings back into Jenkin UI controls on click on Jenkin Job - Save/Apply
6. Submitting Website and Workflow scan setting and initiate on click of Jenkin Job- Build.

### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x ] Please describe what you did
- [x] Link to relevant issues in GitHub or Jira
- [ ] Link to relevant pull requests, esp. upstream and downstream changes
- [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Put an x into the [ ] to show you have filled the information. The template comes from https://github.com/jenkinsci/.github/blob/master/.github/pull_request_template.md You can override it by creating .github/pull_request_template.md in your own repository -->