add a setting to enable/disable telemetry

[vabarbosa]

Description

this PR adds a new qiskitCodeAssistant.enableTelemetry setting to enable/disable whether telemetry is collected for the extension.

Linked Issue(s)

Fixes #98

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

manually tested the setting on and off and confirmed whether data was sent to and collected by the server.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[cbjuan]

We should extend the comment in GETTING_STARTED.md to reflect which kind of telemetry we do gather

[vabarbosa]

We should extend the comment in GETTING_STARTED.md to reflect which kind of telemetry we do gather

good idea! the comment has been updated to reflect what is collected.

any feedback on the phrasing is appreciated. thanks

[cbjuan]

Last comments before approval. Looks good!

[cbjuan]

Suggested change

	1. The Telemetry can be disabled by unchecking the `qiskitCodeAssistant.enableTelemetry` setting or turning `off` the `telemetry.telemetryLevel` setting:
	> **NOTE**: The telemetry does not collect your code nor the suggested code completions. What is collected is whether a code suggestion was accepted or dismissed.
	2. The Telemetry can be disabled by unchecking the `qiskitCodeAssistant.enableTelemetry` setting or turning `off` the `telemetry.telemetryLevel` setting:
	> **NOTE**: The telemetry does not collect your code nor the suggested code completions. What is collected is whether a code suggestion was accepted or dismissed.

shouldn't it be 2 in the numbering?

[cbjuan]

Let's add the same to the README after the /~https://github.com/Qiskit/qiskit-code-assistant-vscode?tab=readme-ov-file#keyboard-shortcuts so we do the same as in jupyterlab

[vabarbosa]

shouldn't it be 2 in the numbering?

it doesnt matter. the markdown rendering/preview will update/display the numbering correctly. i tend to just use all 1.'s so i dont have to worry about keeping them updated accordingly as we add/remove items from list.

Let's add the same to the README after the /~https://github.com/Qiskit/qiskit-code-assistant-vscode?tab=readme-ov-file#keyboard-shortcuts so we do the same as in jupyterlab

done! 23e7a76

[cbjuan]

Let's go!