Connect isSymmetric kernel to DaphneDSL

[gghsu]

This pull request addressed Issue #959 by connecting isSymmetric-kernel to DaphneDSL.

To achieve this, I did following modification:

1. Add instantiated/precompiled for relevant combinations of data types (e.g., DenseMatrix and CSRMatrix) and value types (e.g., double and int64_t) in src/runtime/local/kernels.json
2. Add a DaphneIR operation IsSymmetricOp in src/ir/daphneir/DaphneOps.td
3. Add a DaphneDSL built-in function isSymmetric that generates an IsSymmetricOp in the IR in src/parser/daphnedsl/DaphneDSLBuiltins.cpp.
4. Add script-level test cases for the new DaphneDSL built-in function in test/api/cli/operations/isSymmetric_1.daphne.
   
5. Add Boolean value in ValueTypeCode Enum.

Though it builds successfully and passes all the testcase, there is a warning as below which happens in build process. I think it might due to the new boolean output type, however, I'm not sure how to fix it at this time.

[pdamme]

Thanks for this contribution, @gghsu! It's great to finally connect the isSymmetric-kernel to DaphneDSL to offer it to users. Your code looks good to me.

I only applied some minor improvements, e.g., formatted the code to make the CI code style checks pass, added the new built-in function to the user documentation, and moved the definition of IsSymmetricOp in DaphneOps.td close to the other meta-data-related ops. Furthermore, your changes related to the ValueTypeCode BOOL were not strictly required for this PR, so I undid them. See the commit I added for details. Nevertheless, these are just minor editorial changes; overall, you did very good work!

---

Congrats on your first contribution to DAPHNE! It would be great to see more PRs from you in the future :) .

[pdamme]

Though it builds successfully and passes all the testcase, there is a warning as below which happens in build process. I think it might due to the new boolean output type, however, I'm not sure how to fix it at this time.

This warning is from inside the ANTLR library. We should fix that at some point (maybe by upgrading to a newer version of ANTLR), but that's not related to this PR :) .