Change in error returned when non-existing bucket used in function creation

I'm primarily creating this ticket to clarify that this change in behaviour is intended.

I have a test in my Go SDK test suite (https://github.com/couchbase/gocb/blob/master/cluster_eventingmgr_test.go#L111) which creates an eventing function with a bucket that doesn't exist. In 7.1.0 (and before) I would receive a bucket not found error (strings.Contains(strBody, "ERR_BUCKET_MISSING")), In 7.1.1-3135 I'm receiving a collection not found error (strings.Contains(strBody, "ERR_COLLECTION_MISSING")).

As an aside, I've just noticed that there are now error codes included in the error bodies - I don't believe that there were previously? Where can we find a list of error codes?