fix: Revise length of generated GitHub issue link to avoid hitting URI max length

[stalgiag]

This PR truncates conflict markdown when a "Raise an issue" link has more than 8k chars.

Assumptions:

• 8k was tested in Chrome, Firefox, and Safari. It works on all. There is conflicting information about the limits for Edge but the most up-to-date info suggests that it shares Chrome's limit which would make sense.
• I couldn't create a testing scenario in which anything other than conflict markdown creates an issue link that exceeds this limit. If a reviewer believes otherwise please let me know.

This PR isn't entirely satisfying as it does result in truncated data in the issue. I tried to mitigate the worst effects of this by including a link back to the originating location. I looked into other options but the tradeoffs didn't seem worth it.

Alternatives

• Creating a GH issue via post to GH API
  • pros: no limitation on content
  • cons: would come from a central account rather than users' personals
• Replacing body with a link to a central view of the relevant info in the app
  • pros: no limitations on content, freedom with presentation
  • cons: requires navigating away from GH

related to #1334

[howard-e]

Thanks for addressing. This seems like a safe enough solution to move forward with!

On the alternatives, GH API would definitely be a solid and long lasting solution. The in-app view sounds like a larger buildout of the /conflicts page. And with it just being considered an alternative (but always available) if GH cannot take all the content doesn't really place it as too much of a con for me! At a glance, the latter feels more favorable to me right now.

There may also be very minor changes and removal of some unnecessary white space in the template builder but not enough savings for me to require that be done right now.

Other than that, left an inline comment on the truncated text message.

[howard-e]

Since we now have the conflicts page, this message may have to hold additional context or be more generic. If it's done from the /conflicts, there wouldn't be a "Review Conflicts" button to click.

If you want to avoid passing in additional context, maybe something like 'Content truncated due to URL length limits. Please visit link to review the conflicts.' (and if testSequenceNumber is available, could also append something along the lines of "for Test sequenceNumber")?

[stalgiag]

I forgot about that page! Thanks for reminding me. I took on your suggestion for messaging with 002aa6f

[howard-e]

Confirmed internally that the changes work as expected. Thanks for sorting this out @stalgiag!