Enable issue and custom field population in issue creation for external users

Description

Add the ability to include custom fields in the issue creation screen for external share users.
This feature should allow users to view and modify custom fields when creating issues.

Accepted criteria

Custom fields should be visible and editable for external share users in the issue creation screen.
We should read what fields are required on create screen and allow external user to edit them

Fields

Only found as “single” (non array type):

Type	system	custom	notes
any		`com.pyxis.greenhopper.jira:gh-lexo-rankcom.atlassian.jpo:jpo-custom-field-parentcom.atlassian.jira.ext.charting:timeinstatuscom.atlassian.jconnect.jconnect-plugin:locationcom.pyxis.greenhopper.jira:gh-epic-link... more ...`	❌ No need to support it right now. Maybe once will will integrate with some plugins.
comments-page	comment	❌
date	duedate	`com.atlassian.jira.plugin.system.customfieldtypes:datepickercom.atlassian.jpo:jpo-custom-field-baseline-startcom.atlassian.jpo:jpo-custom-field-baseline-end`	✅
datetime	statuscategorychangedate, resolutiondate, lastViewed, created, updated	`com.atlassian.jira.plugin.system.customfieldtypes:datetimecom.atlassian.servicedesk:sd-request-feedback-datecom.atlassian.jira.ext.charting:firstresponsedateread-only-date-issue-field... more ...`	✅
issuerestriction	issuerestriction		❌ no need to support it
number	timespent, timeoriginalestimate, aggregatetimespent, aggregatetimeestimate, workratio, timeestimate, aggregatetimeoriginalestimate	`jira.polaris:formulajira.polaris:booleancom.atlassian.jira.plugins.proforma-managed-fields:forms-locked-field-cftypecom.atlassian.jira.plugins.proforma-managed-fields:forms-total-field-cftype... more ...`	✅
object		`... some auto-generated trash ...`	❌
option-with-child		`com.atlassian.jira.plugin.system.customfieldtypes:cascadingselect`	✅
priority	priority		✅
progress	aggregateprogress, progress		✅
project	project	`com.atlassian.jira.plugin.system.customfieldtypes:project`	✅
resolution	resolution		✅
sd-approvals		`com.atlassian.servicedesk.approvals-plugin:sd-approvals`	❌
sd-customerrequesttype		`com.atlassian.servicedesk:vp-origin`	✅
sd-feedback		`com.atlassian.servicedesk:sd-request-feedback`	❌
sd-request-lang		`com.atlassian.servicedesk.servicedesk-lingo-integration-plugin:sd-request-language`	✅
sd-servicelevelagreement		`com.atlassian.servicedesk:sd-sla-field`	✅
securitylevel	security		❌ no need to support it
status	status		✅
team		`com.atlassian.jira.plugin.system.customfieldtypes:atlassian-team`	✅
timetracking	timetracking		❌
votes	votes		❌
watches	watches		❌

Only as array:

Type	system	custom	notes
issuelinks	subtasks, issuelinks		❌
attachment	attachment		✅
worklog	worklog		❌
json		`com.pyxis.greenhopper.jira:gh-sprint`	❓ Needs research
sd-customerorganization		`com.atlassian.servicedesk:sd-customer-organizations`	✅
component	component		✅
service-entity-field		`com.atlassian.jira.plugins.service-entity:service-entity-field-cftype`	✅
cmdb-object-field		`com.atlassian.jira.plugins.cmdb:cmdb-object-cftype`	❓ Needs research
sd-asset		`com.atlassian.servicedesk.assets-plugin:assetfield`	❓ Needs research

Mixed, found as single and as array:

Type	system	custom	notes
option		`com.atlassian.jira.plugin.system.customfieldtypes:selectcom.atlassian.jira.plugin.system.customfieldtypes:multicheckboxescom.atlassian.jira.plugin.system.customfieldtypes:jwm-categorycom.pyxis.greenhopper.jira:gh-epic-statuscom.atlassian.jira.plugin.system.customfieldtypes:multiselectcom.atlassian.jira.plugin.system.customfieldtypes:radiobuttons`	✅
user	creator, assignee, reporter	`com.atlassian.jira.plugin.system.customfieldtypes:peoplecom.atlassian.jira.plugin.system.customfieldtypes:multiuserpickercom.atlassian.servicedesk:sd-request-participantscom.atlassian.jira.plugin.system.customfieldtypes:userpickercom.atlassian.jira.toolkit:participants... more ...`	✅
string	labels, description, summary, environment	`jira.polaris:intervalcom.atlassian.jira.plugin.system.customfieldtypes:textarearead-only-string-issue-fieldcom.atlassian.jira.plugin.system.customfieldtypes:textfieldcom.atlassian.jira.plugin.system.customfieldtype... more ...`	✅ This requires research. How to know if this is rich text and which one is simple string? Only by ‘custom’ field? For rich text we need to use custom WYSIWYG editor. Labels - simple comma separated string.
version	fixVersions, versions	`com.atlassian.jira.plugin.system.customfieldtypes:versioncom.atlassian.jira.plugin.system.customfieldtypes:multiversion`	✅
group		`com.atlassian.jira.plugin.system.customfieldtypes:multigrouppickercom.atlassian.jira.plugin.system.customfieldtypes:grouppicker`	✅
option2		`com.atlassian.plugins.atlassian-connect-plugin:com.gebsun.plugins.jira.issuechecklist__issue-checklist-templatescom.atlassian.plugins.atlassian-connect-plugin:eu.softwareplant.bigpicture__modecom.atlassian.plugins.atlassian-connect-plugin:eu.softwareplant.bigpicture__risk-probabilitycom.atlassian.plugins.atlassian-connect-plugin:eu.softwareplant.bigpicture__risk-consequencecom.atlassian.plugins.atlassian-connect-plugin:io.tempo.jira__team... more ...`	❓ Requires research