sqs plugin does not use credentials store, thus forcing to add credentials into an xml file on filesystem.

This is not a good approach, and jenkins already has infrastructure to handle this.

Done criteria: Handle below use case

As jenkins administrator

I want to be able to

1. configure a new SQS queue in Global Configuration by filling in:

• Queue URL/nick name
• choosing existing AWS Credentials, OR adding a new item of AWS credentials

In case I want to force my own Queue Id I should press 'Advanced' checkbox and overwrite automatically generated one.

When manually sending the queue the field should validate the id is indeed unique and not accept already existing Id.

Saving the details should be done using "Save".

After saving the Queue item, its Id should become Immutable

Also, rressing on "Advanced" should still display the Queue Id string.

2. edit an existing SQS queue in Global Configuration by filling mutable details:

• Queue URL/nick name
• Choosing a different AWS credentials (or adding new one)

As jenkins administrator automation developer 

I want to be able to control the plugin parameters with the same level of flexibility as via Web UI.