The counter used in the script recording has assigned a variable name for one http request, rather than a counter value

### Expected behavior

This is a minor issue for me but but unexpected, since it casts doubt on the logic used for this function.
I expect to record a test script with Test Script Recorder and use a format string naming scheme and set counter to 001 and when all actions in the script are complete I will see a sequence of http requests in numerical order.
Format used is #{counter,number,000} - #{path} (#{name})

### Actual behavior

The sequence was correct until it got to 443 - instead of writing:
"443 - /usrsvcs etc etc" I got this:
"${PORT} - /usrsvcs etc etc".
All of the numbers up to and after 443 are correct.
I happen to have a User defined Variable in my test plan with name 'PORT' and value of 443.

### Steps to reproduce the problem

Create Test Plan
Add User Defined Variables with entry: 'PORT' and value 443
Add Recording Controller
Add HTTP Test Script Recorder and naming scheme is use Format String: #{counter,number,000} - #{path} (#{name})
Add View Results Tree
start recording website activity such that you get at least 443 http transactions. I would suggest using some sort of mapping application that generates a lot of requests.
Keep an eye on the Recording Controller and see whether request 443 is named differently from its neighbours.

### JMeter Version

5.6.2

### Java Version

Oracle JDK 17.0.2

### OS Version

Windows 10 10.0.19045 Build 19045