Sliding expiration is limited to 3 minutes and 34 seconds

When trying to add FASTERCache to an ASP.NET Core application with Sessions, I ran into the following exception:

fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
      An unhandled exception has occurred while executing the request.
      System.OverflowException: Arithmetic operation resulted in an overflow.
         at FASTERCache.DistributedCache.GetExpiryTicks(DistributedCacheEntryOptions options, Int32& sliding) in /_/src/FASTERCache/DistributedCache.cs:line 307
         at FASTERCache.DistributedCache.WriteValue(ReadOnlySequence`1 value, Byte[]& lease, DistributedCacheEntryOptions options) in /_/src/FASTERCache/DistributedCache.cs:line 64
         at FASTERCache.DistributedCache.WriteAsync(String key, ReadOnlySequence`1 value, DistributedCacheEntryOptions options, CancellationToken token) in /_/src/FASTERCache/DistributedCache.cs:line 373
         at Microsoft.AspNetCore.Session.DistributedSession.CommitAsync(CancellationToken cancellationToken)

This is because code the SlidingExpiration is converted to ticks and then to an integer:

https://github.com/mgravell/FASTERCache/blob/6f8f2a1e25b819b7cdc8af78a8c2b748780638b0/src/FASTERCache/DistributedCache.cs#L441

Because of this, the max value of SlidingExpiration is 00:03:34.
For my issue, changing the max session to IdleTimeout to 3 minutes fixes this problem:

builder.Services.AddSession(options =>
{
    options.IdleTimeout = TimeSpan.FromMinutes(3);
});

However, 3 minutes is quite small for an idle timeout causing FASTERCache being unusable in this case.

Start in src/FASTERCache/DistributedCache.cs at GetExpiryTicks around line 307 and the SlidingExpiration conversion referenced near line 441. Reproduce the issue with an ASP.NET Core session IdleTimeout above three minutes, then verify that a longer sliding expiration no longer causes an arithmetic overflow.