Update PDFObjectParser.ts

[UnderKoen]

What?

Closes an memory leak.

Why?

When combing many large PDF's the memory usage is through the roof.

How?

By creating an new buffer instead of an view the reference to the orginal buffer is removed and can be picked up on garbage collection.

Testing?

New Dependencies?

No

Screenshots

N/A

Suggested Reading?

No

Anything Else?

Checklist

• I read CONTRIBUTING.md.
• I read MAINTAINERSHIP.md#pull-requests.
• I added/updated unit tests for my changes.
• I added/updated integration tests for my changes.
• I ran the integration tests.
  • I could not build the project locally? No clue why. Same issue as Can't build the dist #1630
• I tested my changes in Node, Deno, and the browser.
• I viewed documents produced with my changes in Adobe Acrobat, Foxit Reader, Firefox, and Chrome.
• I added/updated doc comments for any new/modified public APIs.
• [z] My changes work for both new and existing PDF files.
• I ran the linter on my changes.

[UnderKoen]

After some more testing I don't think this is the solution to the problem. When an Buffer (Node) is supplied this is an issue because Node slice returns an view.