MNT-17914 The build shouldn't depend on Bamboo specific variables.

* Remove direct references to bamboo variables.
   * Revision number is still included.
   * root/packaging/distribution-docker/build.sh still contains refs
     but looks broken already as $bamboo_planRepository_1_branch does
     not exist.

   - Changed poms to have properties that have dummy values for development but
     can be overriden by the bamboo build. These are:
        <build-number>0</build-number>
        <build-key>BUILD-KEY</build-key>
        <build-name>Build-Name</build-name>
        <scm-path>local/development/workspace</scm-path>
        <scm-revision>100000</scm-revision>

   - The bamboo build task use the following arguments:
        -Dbuild-number=${bamboo.buildNumber}               // existing
        -Dbuild-key=${bamboo.buildKey}                     // new
        -Dbuild-name=${bamboo.planName}                    // new
        -Dscm-path=${bamboo.repository.svn.repositoryUrl}  // deprecated #1
        -Dscm-revision=${bamboo.planRepository.1.revision} // existing
     #1 would like to replace with bamboo.repository.1.repositoryUrl which
        is documented but does not exist.

   - Stop using the following bamboo varaibles:
         bamboo.fullBuildKey                          // did not exit
         bamboo.planRepository.revision               // undocumented #2
         bamboo.custom.svn.lastchange.revision.number // deprecated #2
     #2 replaced by bamboo.planRepository.1.revision which is also depreacted
        but it helps if we get the same value from one place.


git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/5.2.N/root@136874 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261

pom.xml

@@ -10,10 +10,7 @@
     </parent>
 
     <properties>
-        <build-number>0</build-number>
-        <scm-revision>123456</scm-revision>
         <repositoryTestIncludes>**/org/alfresco/Repository*TestSuite.java</repositoryTestIncludes>
-        
     </properties>
     
     <dependencies>