Fix no-ref-as-operand and allow lint when ref as right operator

[lakb248]

fix #2271

[ota-meshi]

Thanks for this PR.
However, I think that this PR change has caused false positives in the following usages.

<script setup lang="ts">
import { ref, Ref } from 'vue'
const refValue1: Ref<number>  = ref(0)
const maybeRefValue: Ref<number> | null = getMaybeRef()
const refValue2 = maybeRefValue || refValue1
console.log(refValue2.value)
</script>

I think we should keep track of how the result of the expression is used.
Also, I think the ternary operator could be improved if it would be possible to track the usage of the result of the expression.

[ota-meshi]

#2273 (comment)

[grindpride]

@ota-meshi @lakb248
Maybe put the logic for this rule in a separate no-ref-as-operand-strict rule, or customize with a parameter (strictCheck) of the current one?
In my code there are no cases of the following type

const refValue1: Ref<number>  = ref(0)
const maybeRefValue: Ref<number> | null = getMaybeRef()
const refValue2 = maybeRefValue || refValue1

But errors with such case use are often encountered

const refValue1: Ref<number>  = ref(0)
if (refValue1) {
  //incorrect condition
}