628 table attribute table

[KaylaKremer]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
• Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• Check the commit's or even all commits' message styles matches our requested structure.
• Check your code additions will fail neither code linting checks nor unit test.

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Issue Number: #628

What is the new behavior?

• Adds the mapLayerId to URLs generated in the CMS in order to retrieve the table attribute data.

Does this introduce a breaking change?

• Yes
• No

Other information

This is a CMS specific issue and needs to be tested out!

[SwampGuzzler]

This succeeds in this particular build but breaks attribute tables in other countries. For an example, see this config: 43548e1

[KaylaKremer]

Liberia Build: http://alpha.blueraster.io/gfw-mapbuilder/628-attribute-table-liberia/
Cameroon Build: http://alpha.blueraster.io/gfw-mapbuilder/628-attribute-table-cameroon/
Georgia (The build we're having issues with!): http://alpha.blueraster/gfw-mapbuilder/628-attribute-table-georgia/

[SwampGuzzler]

Let's get this up to the CMS to test CMR and DRC --> we still need to understand why the features in the Georgia application have a _layer.id property of layers that aren't Really in the map at all: PA_4 vs PA