Refactored validation within GeneralCommands and various warnings

[mcllsti]

PR contains improvements to code base and its readability:

• Validation code wtihin GeneralCommands has been refactored to cut down on alot of repetitive checks that have been pulled out into a seperate function
• Tackled two instances of an async method acting synchornous by default, Task.FromResult was used to keep same sync/async flow but to show intentions more clearly.
• Disabled nullable references in various ORM classes where it made sense to do which also removed nullable warnings. There may be scope in the future to consider logic to explicitly tackle them but disabling makes more sense with their current use.
• Small code changes that also tackle nullable warnings where it made sense to do so.

Only a single warning should be left in the solution.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[pauliusdotpro]

Wouldn't be better to add null!; for each property instead. For example:
public string Id { get; set; } = null!;

[SmushyTaco]

Wouldn't be better to add null!; for each property instead. For example: public string Id { get; set; } = null!;

Wouldn't declaring the types as nullable be better? So instead of:

public string Id { get; set; } = null!;

Where you're fighting the compiler to force null into a non null value, you just do:

public string? Id { get; set; };

to properly tell the compiler that the value can be null instead?

[pauliusdotpro]

Review comment