Adding support for issue-body with more than 65536 words, issue body to be created as an issue comment

[snskArora]

This has PR 2 major changes:

• The issueBody is split into chunks of less than 65536 characters.
  Manual approval required for workflow run 14009106423 snskArora/first_go_project#9
  This has an issue body of lorem ipsum of 1,00,000 words.
• Have static issue body and the input of issue body as comment/s
  The previous change with which the issueBody was added in the NOTE block makes any decent-sized approval body difficult to read.

Note

Please perform a squash merge so as to not hinder ease of commit tracking as there are quite a few incoming commits.

[snskArora]

This would resolve #89

[snskArora]

@lizziemac @beverts312, please review this PR. It would be a nice feature to have within the new release.

[lizziemac]

@snskArora this looks good, and it works, however there are couple issues and questions:

• the reported max is characters, not words
• some users can see character limits of 200k+, depending on the zipped size of the issue/comment https://github.com/orgs/community/discussions/41331?utm_source=chatgpt.com#discussioncomment-4366258
• we should limit to characters, not words, and have that limit be 65536, even though it seems sometimes (even in your real-life test) it works beyond that, to ensure this is supported for everyone
• was the issue body supposed to be in the issue message, then split from there? or are we just automatically making it a comment if it's detected to be too big? your example you provide only has the message in the comments.

[snskArora]

• The looping is done over words, but the limit threshold is in characters only. I am processing over words to avoid breaking a word between two comments. The only bottleneck it creates is that if a word is more than 65536 characters, it will fail.

• Earlier, it was in a single comment, but now, since we are going to have an issue comment, I feel it would be better to have the approval body as a separate block than instructions on working with the approval, for better clarity.

[lizziemac]

The looping is done over words, but the limit threshold is in characters only. I am processing over words to avoid breaking a word between two comments. The only bottleneck it creates is that if a word is more than 65536 characters, it will fail.

ah my bad, I think I was a little quick when reviewing. please update the PR name though

Earlier, it was in a single comment, but now, since we are going to have an issue comment, I feel it would be better to have the approval body as a separate block than instructions on working with the approval, for better clarity.

noted. I think that's fine

[lizziemac]

good to merge, just update the PR name and make 65536 a constant/var