Adding Archive Reader implementation

[lemonade-dm]

Archive Gem changes

Adding complete implementation of the new Archive ArchiveReader API

This pairs with the implementation of the ArchiveWriter API and
therefore can be used to write and O3AR archive files.

The Archive Reader supports the following operations

1. ListFileInArchive - This function can query a file within an
   archive by file path or file token which was queried previously from
   a ListFileInArchive call
2. ExtractFileFromArchive - This function can extract file from the
   archive using either the relative file path of the contained file or
   the file token queried from a call to ListFileInArchive
   The file is extracted to a user provided allocated buffer via an
   AZStd::span<AZStd::byte> paramter
3. EnumerateFilesInArchive - This functions enumerates all non-deleted files within the archive and invokes a user provided callback with the ArchiveListFileResult structure for each file. The ArchiveListFileResult structure is the same type returned by ListFileInArchive

Archive Factory addition

Added an Archive Reader and Writer Factory implementation

The Archive Reader Factory allows IArchiveReader instances to be created
by external Client gem modules by depending on the Archive.Clients.API target

The Archive Writer Factory allows IArchiveWriter instances to be created
by external Tool gem modules by depending on the Archive.Tools.API
target.

This other Gems such as the AssetValidation or some other library such as the AssetBundler to create Archive class instances needed to interact with the API

Compression Gem changes

Adding a new interface function of GetCompressionAlgorithmName to the ICompressionInterface/IDecompressionInterface interfaces.
Overriding this function can used to provide a human readable name associated with the Compression algorithm

The plan for this change is to make it easier for a future CLI to allow uses to specify the compression algorithm to use when adding files to an archive.

How was this PR tested?

Added UnitTest for the ArchiveReader functionality to the Archive.Editor.Tests module
Validated the existing ArchiveWriter test still passes.

[spham-amzn]

The blockCount <= MaxBlocksNoJumpEntry is checked before using this function in the lines below, so is this check necessary here?

[lemonade-dm]

No it is not.
I'll remove in this PR if there is a need for a non-trivial update.

[spham-amzn]

Also make sure which logic is right. The one below returns zero, this one returns MaxBlocksNoJumpEntry if blockCount <= MaxBlocksNoJumpEntry

[lemonade-dm]

Well the inner lambda condition is always returning the "else" part of the Ternary since the condition is checked before calling it.

The entire purpose of the two function is to return the minimum block index for the final set of block lines that don't have a jump entry (confusing and hard to explain, I know).

But pretty much every compressed file in the Archive that is >16 MiB starts with its first block line (index 0) with a jump entry.
And then every three block lines afterwards(index 3, 6, 9, ...) would have a Jump entry if there more than 18 MiB (9 blocks) remaining in the file from the start of that block line.

It is explained better in the Streaming Archive document at here, but the implementation is complicated.

[spham-amzn]

Mostly notes on comments/docs. nice work