Fix parenthesized const tag parsing

Fixed an issue where `{@const}` tags with parenthesized initializers (like `{@const x = (a)}`) had incorrect end positions in the parser output, causing source slices and tooling to get unbalanced code ranges. The fix uses the actual parser position instead of the expression node's end position to capture the closing parenthesis.