Bitbucket example README update

[savitaashture]

Changes

1. Updated bitbucket triggerbinding to point http instead of ssh.
2. Updated repository data for bitbucket readme in the format it comes from bitbucket server.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Release Notes

None

[dibyom]

/kind documentation

[dibyom]

/approve

Just one question: What is the motivation behind this change?

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dibyom]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[khrm]

/lgtm

[savitaashture]

Just one question: What is the motivation behind this change?

@dibyom

1. The changes are just to make sure README is in align with the actual output from bitbucket server
   actually when i started testing with real bitbucket server i observed that the response coming in this way

				"links": {
					"clone": [{
						"href": "http://bitbucket-service-bitbucket.apps.cicd.tekton.codereadyqe.com/scm/hel/firstapp.git",
						"name": "http"
					}, {
						"href": "ssh://git@bitbucket-service-bitbucket.apps.cicd.tekton.codereadyqe.com/hel/firstapp.git",
						"name": "ssh"
					}],
					"self": [{
						"href": "http://bitbucket-service-bitbucket.apps.cicd.tekton.codereadyqe.com/projects/HEL/repos/firstapp/browse"
					}]
				}

But in README i have kept clone data in apposite way so in order to make sync modified this way

2. In triggerbinding gitrepositoryurl always pointing to ssh but sometime ssh require extra credential management so in order to make it simple modified to point to http

[khrm]

/lgtm

[vdemeester]

/lgtm

[dibyom]

Just one question: What is the motivation behind this change?

@dibyom

1. The changes are just to make sure README is in align with the actual output from bitbucket server
   actually when i started testing with real bitbucket server i observed that the response coming in this way

				"links": {
					"clone": [{
						"href": "http://bitbucket-service-bitbucket.apps.cicd.tekton.codereadyqe.com/scm/hel/firstapp.git",
						"name": "http"
					}, {
						"href": "ssh://git@bitbucket-service-bitbucket.apps.cicd.tekton.codereadyqe.com/hel/firstapp.git",
						"name": "ssh"
					}],
					"self": [{
						"href": "http://bitbucket-service-bitbucket.apps.cicd.tekton.codereadyqe.com/projects/HEL/repos/firstapp/browse"
					}]
				}

But in README i have kept clone data in apposite way so in order to make sync modified this way

1. In triggerbinding gitrepositoryurl always pointing to ssh but sometime ssh require extra credential management so in order to make it simple modified to point to http

Thanks for the clarification!