DOC: specify k2700 cpts are for ranges

[KaushikMalapati]

Description

I added 'range' to the doc attributes and names of the components dcv, acv, dci, and aci of the K2700 class.

Motivation and Context

I originally thought that the pvs associated with these components were to readback the values in their names, i.e. GetDCV would read the direct current voltage, but they actually get the range configured for each measurement. You use :Reading to get the actually measurement.

How Has This Been Tested?

N/A

Where Has This Been Documented?

New upcoming release notes

Pre-merge checklist

• Code works interactively
• Code contains descriptive docstrings, including context and API
• New/changed functions and methods are covered in the test suite where possible
• Test suite passes locally
• Test suite passes on GitHub Actions
• Ran docs/pre-release-notes.sh and created a pre-release documentation page
• Pre-release docs include context, functional descriptions, and contributors as appropriate

[tangkong]

So this is technically a sort of "API Break", since we're changing the name of a component on this device. If there are older scripts that expect K2700.dcv, they won't be able to find that name any longer.

Practically, if you know you're the only one using this device and you won't break others' usage of the device, this is fine. I just want to make sure this is the case.

If it were me I'd update the documentation alone, but that may be out of an abundance of caution

[KaushikMalapati]

Thanks for the clarification, release notes have been updated to note the API breaks. I recently added this device class and there aren't any happi entries using it other than one I made so it should be safe to change the component names.

[tangkong]

LTGM, thanks for keeping the docs clear 👍