Proposal: remove all try-catch style codes

[hangxie]

This is to follow up #395, all existing recover calls are doing Java/C++ try-catch style error handling, which makes things hard to debug due to lack of call stack.

For example, #452 reports problem without any source file and line numbers, after removing all recover calls, I got:

$ go run type_alias.go
2022/04/17 08:17:13 Write Finished
panic: reflect.Set: value of type int32 is not assignable to type main.AgeInt

goroutine 33 [running]:
reflect.Value.assignTo({0x104d25680?, 0x104eddc48?, 0x104d480c0?}, {0x104ca6af7, 0xb}, 0x104d25800, 0x0)
	/opt/homebrew/Cellar/go/1.18.1/libexec/src/reflect/value.go:3062 +0x210
reflect.Value.Set({0x104d25800?, 0x14000283258?, 0x0?}, {0x104d25680?, 0x104eddc48?, 0x0?})
	/opt/homebrew/Cellar/go/1.18.1/libexec/src/reflect/value.go:2088 +0xcc
github.com/xitongsys/parquet-go/marshal.Unmarshal(0x140002846c8, 0x6, 0x9, {0x104d1ae60?, 0x14000283200}, 0x140002a5c70, {0x0, 0x0})
	/Users/xiehang/dev/parquet-go/marshal/unmarshal.go:228 +0xc84
github.com/xitongsys/parquet-go/reader.(*ParquetReader).read.func2(0x0?, 0x0?, 0x2)
	/Users/xiehang/dev/parquet-go/reader/reader.go:336 +0x11c
created by github.com/xitongsys/parquet-go/reader.(*ParquetReader).read
	/Users/xiehang/dev/parquet-go/reader/reader.go:330 +0x4c8
exit status 2

which makes it super easy to fix.

This PR may cause panic for those who depend on parquet-go in near future, but we can collect all those panic cases and fix them by adding extra check on incoming data/parameters.

I used patched version with my personal project, it just works without any problems.