Added usage examples to some APIs

[msteknoadam]

Added usage examples to these APIs

• image.random_flip_up_down
• image.flip_up_down
• image.random_flip_left_right
• image.flip_left_right
• image.transpose
• image.random_brightness
• image.random_contrast
• image.random_hue
• image.random_jpeg_quality
• image.random_saturation

-- Re-Opened the PR since the last one wasn't based off the master --

[googlebot]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[msteknoadam]

@googlebot I consent.

[kyscg]

@googlebot I consent

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[msteknoadam]

Yeah actually that idea feels good, I will do it ASAP. Thanks for the recommendation!

[mihaimaruseac]

Thanks for the update. However, it still fails to be testable.

I was thinking of something more on the lines of

tensorflow/tensorflow/python/ops/array_ops.py

Lines 100 to 109 in 5078cab

	>>> t = [[1, 2, 3],
	... [4, 5, 6]]
	>>> tf.reshape(t, [3, 2]).numpy()
	array([[1, 2],
	[3, 4],
	[5, 6]], dtype=int32)
	>>> tf.transpose(t, perm=[1, 0]).numpy()
	array([[1, 4],
	[2, 5],
	[3, 6]], dtype=int32)

[msteknoadam]

Hmm yeah, ok. I will be changing them in a few mins.

[msteknoadam]

Ok, made the changes. Can you check again?

[mihaimaruseac]

Looks better but still not there:

• Don't use tf.random.normal as then testing would depend on the seed that is being used. Instead, explicitly use some values (like in the example above, t = [[1, 2, 3],...)
• Use >>> instead of >> as >>> signal that this is documentation test which will then be tested.
• There is no need for the triple backquote markers and the python tagging. The >>> makes this look like properly-formatted code in the documentation.
• Don't insert these examples after the typing/argument documentation, but before that. Args:/Returns:/etc. are expected to always be the last blocks in a docstring.

[mihaimaruseac]

I think you might need to rebase against master again

[msteknoadam]

Sure thing, done!

[msteknoadam]

By the way, I guess last error was a false-triggered error since it was giving 404 when reaching to logs and I have seen that when you re-ran it, it didn't give an error.

[rthadur]

@msteknoadam can you please resolve conflicts

[msteknoadam]

Sorry, I was sleeping at the moment you requestef for changes but thanks for doing the changes for me. I'm very happy that this PR finally got merged :D Have a great day everyone!