[DOCS] Changes to sections for configuring connectors and mapped case fields

[nastasha-solomon]

Addresses the following issues:

• Breaks down the giant table in step 4 into smaller units as per @joepeeples 's suggestion in [DOCS] Consider a widget to focus info in connector topic #2097.
• Makes changes @benironside suggested in [DOCS] Additional updates to consider for mapped field section #2100.
• Revised table with field mapping details as per @joepeeples 's suggestion in [DOCS] Consider expanding table for mapped fields  #2098.

Previews:

• Create a new connector
• Mapped case fields

[benironside]

Looks great overall, left a few minor suggestions and one question.

[benironside]

Suggested change

	*** *All*: You can choose to set all or no field mappings when creating your new {swimlane} connector. However, note that if you don’t set field mappings now, you’ll be prompted to do so if you want to use the connector for a case or a rule.
	*** *All*: You can choose to set all or no field mappings when creating your new {swimlane} connector. However, note that if you don’t set field mappings now, you’ll be prompted to do so before you use the connector for a case or a rule.

[benironside]

This is probably a dumb question because I've never tried out a Swimlane connector, but does this not apply to the other two options here ("Alerts" and "Cases")? I.e. do you not have to map fields if you select one of those? It reads like you don't, so just confirming.

[nastasha-solomon]

Not a dumb question and you're correct! I'll move this to a note under the parent bullet (so under Connector Type) because it does apply to all the types.

[joepeeples]

Awesome reorganization! Forget I ever said anything about a widget; this is clean and easy to follow, and will be easier to maintain, too. One tiny tweak below.

[nastasha-solomon]

Might encounter a merge conflict after pull in changes from #2297. Should accept the changes from this PR.

[mergify]

This pull request is now in conflicts. Could you fix it @nastasha-solomon? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b issue-2097-widget upstream/issue-2097-widget
git merge upstream/main
git push upstream issue-2097-widget

[jmikell821]

Thanks for reorging this! 🎉

[mergify]

This pull request is now in conflicts. Could you fix it @nastasha-solomon? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b issue-2097-widget upstream/issue-2097-widget
git merge upstream/main
git push upstream issue-2097-widget

[nastasha-solomon]

Opened #2417 to start fresh. When I merged in changes from the remote main branch, the changes got applied to my local project branch and then pushed back up the PR - hence the merge conflicts and numerous updated files.