Changed type aliases to type definitions

[0xpanicError]

Changed all type aliases in the sdk to type definitions

What Changed?

here are the types that were changed

// types/avs.go

type TaskIndex = uint32
type TaskResponseDigest = Bytes32

// types/operator.go

type OperatorAddr = common.Address
type StakeAmount = *big.Int
type OperatorId = Bytes32
type BlockNum = uint32

Reviewer Checklist

• Code is well-documented
• Code adheres to Go naming conventions
• Code deprecates any old functionality before removing it

[samlaf]

not sure these explicit type casts are the way to go. If we ever change blockNumber to be uint64 for eg then we'll have to go change these everywhere.

We could define a UnderlyingType() on all the types to unwrap them, which we could use here like blockNumber.UnderlyingType(), but not convinced this is nice either.

Need to think about this more and discuss with @shrimalmadhur

[0xpanicError]

even in the blsagg_test.go file there were 15 instances of blockNum defined as blockNum := uint32(1)
The OperatorStateRetriever takes in blockNum as uint32

should I in the mean time revert the changes made to blockNum ?