Errors returned from ebpf apis should be exported for better testing/development practices

Currently in the codebase we do a lot of `return fmt.Errorf(...)` which is convenient but makes making sure that an error is a certain type a lot harder and creates fragile conditions for testing where we rely a lot on error strings. 

Ideally we should have a list of errors somewhere that we export to users that can then go ahead and use those errors for comparisons, assertions, etc.