What this PR does / why we need it:

Related issue: IQSS/dataverse-client-javascript#244

We would move html to markdown transformation from js-dataverse repo to this frontend repo in dataset pages. We assume we will get raw dataset summary and metadata info from js-dataverse, and then we'll deal with the format transformation issue. Only if the field is in textbox type, we'll transform html tags into markdown.

• Update keepRawField parameter so as to getDataset with raw data
• Update markdown component, allow transforming HTML to markdown
• Update JSMetadataBlockInfoMapper.ts, get type of fields
• Apply markdown component if type == 'TEXTBOX'

Which issue(s) this PR closes:

• Closes Edit Dataset Page: do not transform metadata values to markdown #587

Special notes for your reviewer:

Suggestions on how to test this:

Check the HTML Tags

1. Create a Dataset

• Fill out the form, and give some html tags to fields (especially description field). such as <b> description </b>

2. Check Dataset Summary and MetadataDisplay

• On the dataset page, if it's description (TEXTBOX type), it should shown with the HTML styles and without HTML tags. For instance, test` should render correctly as test (bold).
• If the field is not in TEXTBOX fields, such as subtitle and keywords, should <b>test</b>, not as the rendered bold text or plain text.

3. Edit the Dataset Metadata

• Verify that when the dataset metadata opens for editing, the pre-filled text in fields matches exactly what was entered during creation with html tags.
• On the edit page, the field should display exactly what you entered: <b>test</b>, not as the rendered bold text or plain text.

4. Save Changes and Confirm Updates

• After saving the edited metadata, verify that all changes successfully update on the dataset display page.

Check the underscore escaping
refered to IQSS/dataverse-client-javascript#241

1. Create a Dataset

• Fill out the form, and give some underscores and other symbols to fields. such as __description/title__

2. Check Dataset Summary and MetadataDisplay

• On the dataset page, check if the underscore work well without extra characters or symbols.

3. Edit the Dataset Metadata

• Verify that when the dataset metadata opens for editing, the pre-filled text in fields matches exactly what was entered during creation.

4. Save Changes and Confirm Updates

• After saving the edited metadata, verify that all changes successfully update on the dataset display page.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation: