Added example program outputs (#3892)

[BrandonPacewic]

This pr fixes #3892.

Added program output for example code as well as fixed the compile errors within the equal_range example code.

[ghost]

All CLA requirements met.

[PRMerger15]

@BrandonPacewic : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[Court72]

@TylerMSFT

Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"

[PRMerger19]

@BrandonPacewic : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[PRMerger10]

@BrandonPacewic : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[PRMerger16]

@BrandonPacewic : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[BrandonPacewic]

After looking through more of the documentation it has occurred to me that lots of example code sections do not contain the output of said code. Is this on purpose or because of how each individual decided to write each doc section?

[TylerMSFT]

Thank you for adding the output examples and improving the docs.

[TylerMSFT]

@BrandonPacewic, regarding your question about output samples, yes, it can vary by writer. Some of these docs are very old, were authored at different times when cpub standards and emphasis were different, or came from an earlier publishing system and may have suffered at the hands of automated conversion to the new format. Or someone may have decided that including the output wouldn't add any descriptive value because it was self-evident. Regardless of the reasons, thank you for adding value here. Much appreciated.

[BrandonPacewic]

Absolutely, looking forward to making more contributions when I can.

[TylerMSFT]

#sign-off
I was testing out your code change.