Add span_id to LogEntry

[salrashid123]

Add span_id to LogEntry

Note trace should get specified if span_id is set. The logging API does not currently return an error and while the final displayed log line does have a span_id, its not too useful. Instead of client-side validation, CloudLogging would return exception later (i'll file internal FR for that)

ref:

• Allow specifying LogEntry optional parameters in google.cloud.logging.logger #5505

[salrashid123]

am i missing something in the cover tests? i didn't really do anything there to account for that coverage failure

Name                                                            Stmts   Miss Branch BrPart  Cover   Missing
-----------------------------------------------------------------------------------------------------------
google/cloud/logging/logger.py                                    124      1     58      1    99%   593, 584->593

[tseaver]

@salrashid123 I'm puzzled, too: that branch / line should be covered by test_commit_w_invalid_entry_type.

[salrashid123]

@tseaver Is there a directive you can invoke to rerun the checks (i.e, /oktotest)?

btw, i tried running cover locally but that looks for python3.7

$ nox -f logging/nox.py -s cover
nox > Running session cover
nox > /usr/bin/python -m virtualenv /home/srashid/workspace/github/google-cloud-python/.nox/cover -p python3.6
nox > Command /usr/bin/python -m virtualenv /home/srashid/workspace/github/google-cloud-python/.nox/cover -p python3.6 failed with exit code 3:
The path python3.6 (from --python=python3.6) does not exist
nox > Session cover failed.

i tried changing the session.interpreter= value to python27 in logging/nox.py but that gives other errors

[tseaver]

Nice catch!