Fix Long literal rendering to add L suffix

[Copilot]

When rendering integer number nodes as Document.fromLong(...), the generated literal lacked the L suffix, causing compilation failures (integer number too large) for values exceeding Int.MaxValue (e.g. 1716459630).

Changes

• Renderer.scala: Append L suffix to generated long literals

  - line"smithy4s.Document.fromLong(${x.getValue.longValue()})"
  + line"smithy4s.Document.fromLong(${x.getValue.longValue()}L)"

• Test expectations in DynamicHintRenderingSpec and AwsStandardTypesTransformerSpec updated to match new output
• sampleSpecs/numeric.smithy: Changed the Long field default from 1 to 9999999999 (a value exceeding Int.MaxValue) to provide a concrete test case that validates the fix — without the L suffix, this would fail to compile
• Bootstrapped managed sources regenerated via sbt bootstrapped/managedSources
• CHANGELOG.md: Added entries for the 0.18.48 and upcoming 0.18.49 releases

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Renderer of Long value - integer number too large</issue_title>
<issue_description>This change introduced a breaking change on v0.18.48: 7b2e915#diff-d9b9aaad6d4cbc087589558a913c2bc9e199420e82425b42800823a6c1a09af2R1893-R1897

On renderer:

smithy4s/modules/codegen/src/smithy4s/codegen/internals/Renderer.scala

Line 1896 in 7b2e915

line"smithy4s.Document.fromLong(${x.getValue.longValue()})"

If the long value is actually a long, it doesn't compile with integer number too large.

Previously, it was rendered with smithy4s.Document.fromDouble(${x.getValue.doubleValue()}d) and was working.

I think it can be fixed with the following:

- line"smithy4s.Document.fromLong(${x.getValue.longValue()})"
+ line"smithy4s.Document.fromLong(${x.getValue.longValue()}L)"
```</issue_description>

<agent_instructions>Update the renderer code to add the "L" character. Re-run 'sbt bootstrapped/managedSources' after you're done, and check in the changed files before opening the PR.</agent_instructions>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes Renderer of Long value - integer number too large #1897

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[kubukoz]

@copilot change one of the existing test values (in sampleSpecs/) so that it's too much for a normal integer, and regenerate the code.

[kubukoz]

@copilot also update the CHANGELOG file to include this PR. The next release will be 0.18.49.

[Copilot]

@copilot change one of the existing test values (in sampleSpecs/) so that it's too much for a normal integer, and regenerate the code.

Done in 2080a04. Changed l: Long = 1 to l: Long = 9999999999 in sampleSpecs/numeric.smithy — this value exceeds Int.MaxValue (2,147,483,647), so it would have failed to compile without the L suffix fix. The regenerated Numeric.scala now contains smithy4s.Document.fromLong(9999999999L) and l: Long = 9999999999L.

[Copilot]

@copilot also update the CHANGELOG file to include this PR. The next release will be 0.18.49.

Done in 6f65f28. Added the 0.18.49 entry to CHANGELOG.md.

[kubukoz]

@copilot add the missing CHANGELOG entry for 0.18.48 too

[Copilot]

@copilot add the missing CHANGELOG entry for 0.18.48 too

Done in 44f0529. Added the 0.18.48 entry to CHANGELOG.md with the two PRs from that release (#1886 and #1893).