bitbake: bitbake: Don't limit traceback lengths to arbitrary values

There appears to have been a lot of copy and pasting of the code
which prints tracebacks upon failure and limits the stack trace to
5 entries. This obscures the real error and is very confusing to the user
it look me an age to work out why some tracebacks weren't useful.

This patch removes the limit, making tracebacks much more useful for
debugging.

[YOCTO #9230]

(Bitbake rev: 5549748a200b5df259fc7352477ec59471b87b2f)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake/bin/bitbake-layers

@@ -1068,5 +1068,5 @@ if __name__ == "__main__":
     except Exception:
         ret = 1
         import traceback
-        traceback.print_exc(5)
+        traceback.print_exc()
     sys.exit(ret)

bitbake/bin/bitbake-prserv

@@ -50,6 +50,6 @@ if __name__ == "__main__":
     except Exception:
         ret = 1
         import traceback
-        traceback.print_exc(5)
+        traceback.print_exc()
     sys.exit(ret)
 

bitbake/bin/image-writer

@@ -119,4 +119,4 @@ if __name__ == '__main__':
         gtk.main()
     except Exception:
         import traceback
-        traceback.print_exc(3)
+        traceback.print_exc()

bitbake/lib/toaster/contrib/tts/toasteruitest/run_toastertests.py

@@ -146,7 +146,7 @@ if __name__ == "__main__":
     except:
         ret = 1
         import traceback
-        traceback.print_exc(5)
+        traceback.print_exc()
     finally:
         if os.getenv('TOASTER_SUITE'):
             del os.environ['TOASTER_SUITE']