OpenSystemsDevelopment / qpdf

…ield` function to increase code clarity.

…h `std::list<Dictionary>`, simplify `/Kids` handling, and update method calls for consistency.

…annotation` to increase code clarity.

…h operator[], update type handling for clarity and consistency, and streamline resource merging.

…roFormDocumentHelper`, replace redundant maps with `FieldData` encapsulation.

…n `QPDFOutlineObjectHelper` and `QPDFOutlineDocumentHelper`.

…n `QPDFAcroFormDocumentHelper`.

…e memory management, and streamline class definition.

…e()` for re-validation and repair of AcroForm structure.

…roduce `empty` checks, and use `std::cmp_less` and `emplace_back` for better clarity and efficiency.

…`warn`, streamline condition handling.

Refactored several classes to use C++11 `final` specifiers for inheritance restrictions and added default member initializations. These changes enhance code clarity, improve safety, and ensure modern coding practices.

Simplified checks for empty containers and strings across the codebase using the `.empty()` method. This improves code readability and adheres to best practices for checking emptiness.

Converted multiple occurrences of `count()` to `contains()` throughout the codebase where the goal was to check key existence in containers. This improves code readability and aligns with modern C++ practices, particularly with C++20, making the intent more explicit and potentially aiding performance.

This improves indentation of long strings. This commit also fixes some
trailing whitespace in ChangeLog.

Rather than adding yet another flag that is almost never useful on its
own, just have --remove-restrictions disable digital signatures. The
operations are still separate in the API.

Using search and replace.

For consistency with similar methods, e.g. replaceObject.

Remove any ambiguity around whether old or new value is being
returned.

Also, revert inlining of unparse and operator << from commit 4c6640c in
order to avoid exposing QUtil.

Remove variables obsoleted by commit 4f24617.

I decided these were confusing and inconsistent with how JSON works.
They muddle the API rather than improving it.