Add continuous counter update to VaCounter close #2108

[ghost]

Description

This PR adds a feature to the counter component in Vuestic UI that allows the counter to continuously update when the user keeps the button pressed instead of updating only once. close #2108

Markup:

Relevant code

<template>
  ...
  <va-button class="va-counter__button-decrease" :aria-label="t('decreaseCounter')" v-bind="decreaseButtonProps"
    @click="decreaseCount" @mousedown.prevent="startDecreasing" @mouseup.prevent="stopDecreasing" />
  ...
  <va-button class="va-counter__button-increase" :aria-label="t('increaseCounter')" v-bind="increaseButtonProps"
    @click="increaseCount" @mousedown.prevent="startIncreasing" @mouseup.prevent="stopIncreasing" />
  ...
</template>

<script>
...
let decreaseInterval: number | undefined
let increaseInterval: number | undefined
...
const startDecreasing = () => {
  decreaseCount()
  decreaseInterval = setInterval(decreaseCount, 100) as any
}
const stopDecreasing = () => {
  clearInterval(decreaseInterval)
}
const startIncreasing = () => {
  increaseCount()
  increaseInterval = setInterval(increaseCount, 100) as any
}
const stopIncreasing = () => {
  clearInterval(increaseInterval)
}
...
setup(props, { emit, attrs }) {
  ...
  return {
    ...
    startDecreasing,
    stopDecreasing,
    startIncreasing,
    stopIncreasing,
    ...
  }
}
...
</script>


## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [X ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Improvement/refactoring (non-breaking change that doesn't add any feature but make things better)

[RVitaly1978]

Fix: elements with multiple attributes should span multiple lines, with one attribute per line

[m0ksem]

Looks good. Thanks! Will do QA later. Try to move logic outside this component to composables. We likely will use it for other components like Carousel, Tabs, etc.

Lmk if you need help with this.

[m0ksem]

Hey, @Skander999. Composable looks good, thanks! I simplified it a bit using our existing utility composables like useEvent, useTemplateRef and removed your old implementation in VaCounter, so logic implemented in composable now, not in component.

[m0ksem]

@RVitaly1978, check how your unnecessary refactoring impact other's PR- it was beautiful until I merged develop here to resolve conflicts :) Also, waiting for your review here, and we're ready to merge.

[ghost]

Thank you for your feedback @m0ksem !