Fixed a bug with GetFilteredContentByTag

[degenone]

When navigationg to /Moderation I got an error:

crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: An unexpected error occurred invoking 'GetFilteredContentByTag' on the server.
Microsoft.AspNetCore.SignalR.HubException: An unexpected error occurred invoking 'GetFilteredContentByTag' on the server.
   at Microsoft.AspNetCore.SignalR.Client.HubConnection.InvokeCoreAsyncCore(String methodName, Type returnType, Object[] args, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.SignalR.Client.HubConnection.InvokeCoreAsync(String methodName, Type returnType, Object[] args, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.SignalR.Client.HubConnectionExtensions.<InvokeCoreAsync>d__43`1[[System.Collections.Generic.IEnumerable`1[[TagzApp.ViewModels.Data.ModerationContentModel, TagzApp.ViewModels, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]], System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
   at TagzApp.Blazor.Client.Components.Pages.Moderation.InitializeContent() in C:\Users\terpp\dev\TagzApp\src\TagzApp.Blazor.Client\Components\Pages\Moderation.razor:line 337
   at TagzApp.Blazor.Client.Components.Pages.Moderation.OnInitializedAsync() in C:\Users\terpp\dev\TagzApp\src\TagzApp.Blazor.Client\Components\Pages\Moderation.razor:line 171
   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

Adding the following code to ModerationHub.GetFilteredContentByTag

string negOne = "-1";
Console.WriteLine($"state({state}) == negOne({negOne}) ? {state == negOne} | signs: state({(int)state[0]}) negOne({(int)negOne[0]})");

It prints state(−1) == negOne(-1) ? False | signs: state(8722) negOne(45).

I felt that the simplest change was to have state be an int instead of string and this fixed the bug.