refactor: avoid isTruthy call in places where it's not needed

[crnkovic]

Summary

https://app.clickup.com/t/86drj8rbd

There are some places in React where we have some value be either some object or null. We can avoid calls to isTruthy in these situations as it's simple enough to check whether some value is null or undefined.

Also, if some component prop is an optional boolean, we can default to false, such as in the TextInput component, to avoid this prop being possibly undefined.

For example:

interface Props {
    isDisabled?: boolean;
}

function SomeComponent({ isDisabled = false }: Props) {
    // isDisabled is now always boolean and doesn't need `isTruthy` call
}

Just uses more TypeScript to make a nicer developer experience.

Checklist

• I checked my UI changes against the design and there are no notable differences
• I checked my UI changes for any responsiveness issues
• I checked my (code) changes for obvious issues, debug statements and commented code
• I opened a corresponding card on Clickup for any remaining TODOs in my code
• I added a short description on how to test this PR (if necessary)
• I added a storybook entry for the component that was added (if necessary)
• Documentation (if necessary)
• Tests (if necessary)
• Ready to be merged