Fix Image.Identify/IdentifyAsync byte array/file overloads still referring to a stream argument in documentation

[UnknownShadow200]

Prerequisites

• I have written a descriptive pull-request title
• I have verified that there are no overlapping pull-requests open
• I have verified that I am following the existing coding patterns and practice as demonstrated in the repository. These follow strict Stylecop rules 👮.
• I have provided test coverage for my change (where applicable)

Description

The Image.Identify/IdentifyAsync overloads that took byte arrays or file paths as the input argument still referred to them as a stream in their documentation

[CLAassistant]

All committers have signed the CLA.

[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.}

[dlemstra]

Are we also using encoded in other comments?

[UnknownShadow200]

For byte arrays, IdentifyFormat doesn't call them encoded in <summary> but Load does, so I went with the latter for consistency

Although the <summary> for streams/files doesn't mention encoded at all, so I can remove encoded from <summary> for byte arrays if preferable

[JimBobSquarePants]

Replaced by #2317 as the APIs are being refactored. @UnknownShadow200 thanks for your help here!