feat!: add more integers and unsigned integers

[somebadcode]

• Reintroduced all variants of integers and unsigned integers.

Fixes: #2050

What type of PR is this?

• feature

What this PR does / why we need it:

Only having flags for int64 and uint64 when generics can be used to make it support all of them is very limiting and forces the users of the package to create wrappers if the variable that they want to configure using a flag is not part of their project or adds unnecessary bloat by having less appropriate integer types and conversions of those integers.

Which issue(s) this PR fixes:

Fixes #2050

Release Notes

(REQUIRED)

Added support for all integer types, signed and unsigned.

[dearchap]

@somebadcode Can you run make v3approve and push your changes. That should fix the failing checks.

[somebadcode]

@dearchap I've addressed the things you pointed out and I've added basic tests for all the new flag types.

[xoxys]

This change is breaking again, right? I'm wondering about how this will be released. Will we see v4 soon?

[somebadcode]

This change is breaking again, right? I'm wondering about how this will be released. Will we see v4 soon?

Yes, it's breaking since it changes Int from int64 to int.
So that's what I'm wondering. The same thing has to be done with floats. Not supporting all the builtin types was a huge mistake. The flag package should be the minimum requirement. Any package that try to be an alternative should have the same base feature-set.

I was a bit too slow to make it to the v3 release. I initially hoped that they'd held back the release of v3 because of these mistakes since the use of generics makes is really easy to cover all the different integers and floats.

So maybe correcting these short-comings will cause a v4 in a not too distant future?

[dearchap]

Yes breaking change. Can't help it.