Add support for RANGE op

[fwcd]

This op seems to be used internally by MelSpectrogram layers and would be convenient to have supported.

Potentially related:

• YamNet: Didn't find op for builtin opcode 'RANGE' version '1'. #1042

[HemanthSai7]

The op needs to be ported 😢

[github-actions]

"This issue is being marked as stale due to inactivity. Remove label or comment to prevent closure in 5 days."

[github-actions]

"This issue is being closed because it has been marked as
stale for 5 days with no further activity."

[ddavis-2015]

@fwcd @HemanthSai7 Let's discuss further. TFLM does not have dynamic memory allocation, thus a RANGE operator would be limited to only being supportable with all 3 inputs as constant-tensors. Is this the way it is used in existing models?

[HemanthSai7]

Yeah. I had to remove the usage of range while converting the model to TFLITE. Yes I was using it with dynamic arrays.