Change AMQP default port to non-ssl

We have gone back and forth on this a bit.  But, I believe it's shaken itself
out during testing.

When setting up AMQP to use SSL, several steps are involved including copying
ssl certs from the AMQP server over to the ManageIQ appliance.  Defaulting to
the SSL AMQP port assumes that the user is going to take these steps.  It's
better to assume non-ssl, and then include changing the default AMQP port number
part of the steps for configuring AMQP to use SSL in the appliance.

https://bugzilla.redhat.com/show_bug.cgi?id=1127954
Constantize default amqp port

https://bugzilla.redhat.com/show_bug.cgi?id=1127954
Fix default amqp port setting for qpid connection

There are two problems here:

1) the default port setting of 5671 is assuming SSL connections for AMQP
2) the def_options was actually overriding the values in the options parameter

When setting up AMQP to use SSL, several steps are involved including copying
ssl certs from the AMQP server over to the ManageIQ appliance.  Defaulting to
the SSL AMQP port assumes that the user is going to take these steps.  It's
better to assume non-ssl, and then include changing the default AMQP port number
part of the steps for configuring AMQP to use SSL in the appliance.

Secondly, the direction of the hash merge was taking the default values in
def_options and replacing anything in the options parameter.  Instead, the logic
should be to only use the default values in the def_options local variable when
there are no corresponding values provided in the options parameter.

https://bugzilla.redhat.com/show_bug.cgi?id=1127954
Fix default amqp port setting for rabbit

Two problems addressed here:

1) The default port setting for rabbit connections of 5671 assumes SSL
2) The connect method was not using the value provided by the caller

When setting up AMQP to use SSL, several steps are involved including copying
ssl certs from the AMQP server over to the ManageIQ appliance.  Defaulting to
the SSL AMQP port assumes that the user is going to take these steps.  It's
better to assume non-ssl, and then include changing the default AMQP port number
part of the steps for configuring AMQP to use SSL in the appliance.

Secondly, the connect method was simply ignoring any value for AMQP port
provided by the caller and insisting on 5671.

https://bugzilla.redhat.com/show_bug.cgi?id=1127954
Provide port for qpid connection spec

https://bugzilla.redhat.com/show_bug.cgi?id=1127954
Bump to latest 3.2.17 tag to include a connection retry logic fix.
Merge pull request #359 from blomquisg/bz1127954-amqp-default-port

Bz1127954 amqp default port
Merge pull request #369 from jrafanie/bump_rails_tag

Bump to latest 3.2.17 tag to include a connection retry logic fix.
Post substitution the extra URL encode will be skipped

https://bugzilla.redhat.com/show_bug.cgi?id=1128864

When we do a substitution each component of the substituted string
was subjected to an extra round of URL encoding. This was happening
just for relationships. This extra URL encoding has been removed
till we have a valid usecase for it. With the extra substitution we
would convert a string like TEST/DEMO to TEST%2FDEMO, which is incorrect
without the knowledge about how the string is going to be used.
Merge pull request #357 from mkanoor/ae_substitution_issue_1705

Post substitution the extra URL encode will be skipped