Inconsistent definitions of bitwise not and logical not

[idavis]

In the spec, bitwise negation is represented as ~ and logical not is represented as !.

In crates/oq3_syntax/src/ast/expr_ext.rs the code represents the opposite:

impl ast::PrefixExpr {
    pub fn op_kind(&self) -> Option<UnaryOp> {
        let res = match self.op_token()?.kind() {
            T![~] => UnaryOp::LogicNot,
            T![!] => UnaryOp::Not,
            T![-] => UnaryOp::Neg,
            _ => return None,
        };
        Some(res)
    }

    pub fn op_token(&self) -> Option<SyntaxToken> {
        self.syntax().first_child_or_token()?.into_token()
    }
}

as well as in crates/oq3_syntax/src/ast/operators.rs

#[derive(Copy, Clone, Debug, PartialEq, Eq, Hash)]
pub enum UnaryOp {
    /// `~`
    LogicNot,
    /// `!`
    Not,
    /// `-`
    Neg,
}

In the Qiskit repo, qiskit/qiskit/qasm3/ast.py defines Unary expr as:

class Unary(Expression):
    class Op(enum.Enum):
        LOGIC_NOT = "!"
        BIT_NOT = "~"

    def __init__(self, op: Op, operand: Expression):
        self.op = op
        self.operand = operand

While the Qiskit repo is missing negation (-), I believe the parser needs to be updated to reflect the spec and Qiskit repo for logical and bitwise not.