fix: change the isError to not use the state

[wcarlson5]

since the state ERROR changed definitions the current isError is no longer really relevant. However it actually seems that isError is not used so I will just remove it._

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[ghost]

@confluentinc It looks like @wcarlson5 just signed our Contributor License Agreement. 👍

Always at your service,

clabot

[ableegoldman]

Makes sense to me

[guozhangwang]

Hey @wcarlson5 Could you update the description a bit for the rationales just for my education? Why we should not use the state for isError?

[wcarlson5]

@guozhangwang since the state ERROR changed definitions the current isError is no longer really relevant. However it actually seems that isError is not used so I will just remove it

[ableegoldman]

+1 on putting what you just said in the PR description. Filling out the description just makes it easier to understand what the PR is about at a glance, which is useful eg if we ever have to skim over PRs looking for possible regressions. It's a good idea to always do, even if the changes in the PR are extremely obvious to you

[wcarlson5]

good call. TBH I was going to check with some more testing to see if I needed to remove it (which I can). I probably should have made it as a draft PR first. But thanks for the quick reviews!