[Bug] With `config_mode => "advanced"` mode, plugin doesn't consider `initial_position` from `event_hubs` entries.

[mashhurs]

Logstash information:

Please include the following information:

1. Logstash version (e.g. bin/logstash --version)
2. Logstash installation source (e.g. built from source, with a package manager: DEB/RPM, expanded from tar or zip archive, docker)
3. How is Logstash being run (e.g. as a service/service manager: systemd, upstart, etc. Via command line, docker/kubernetes)
4. How was the Logstash Plugin installed

JVM (e.g. java -version):

If the affected version of Logstash is 7.9 (or earlier), or if it is NOT using the bundled JDK or using the 'no-jdk' version in 7.10 (or higher), please provide the following information:

1. JVM version (java -version)
2. JVM installation source (e.g. from the Operating System's package manager, from source, etc).
3. Value of the JAVA_HOME environment variable if set.

OS version (uname -a if on a Unix-like system):

Description of the problem including expected versus actual behavior:
When using config_mode => "advanced" and setting multiple event hub settings in the event_hubs => [] param, the plugin doesn't use individual param such as initial_position of the each event_hubs entry. Instead it uses a global initial_position.
It looks like here is the bug that should use case event_hub['initial_position'] instead of case @initial_position : https://github.com/logstash-plugins/logstash-input-azure_event_hubs/blob/main/lib/logstash/inputs/azure_event_hubs.rb#L425

Steps to reproduce:

Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.

Provide logs (if relevant):

[phoboselk]

Below is the sample pipeline config to reproduce the issue. With this configuration plugin will check for initial_position in the "global" parameters, and will default to offset[-1]. This has been reproduced on 8.16.2, 8.19.6, 9.2.0

input {
    azure_event_hubs {
       config_mode => "advanced"
       threads => 2
       decorate_events => true
       codec => json {}
       event_hubs => [{
       			"test"=> {   
event_hub_connection => "xxxxxx"
storage_connection => "xxxxxxx"
storage_container => "logstash"
consumer_group => "logstash"
initial_position => "end" 
 		     		}
 		     	}
       		]
   	 }
}

[mashhurs]

@phoboselk , released new 1.5.3 version fixes the bug.