Remove <model>.pte generation from export_bundled_program.py

Summary:
Currently, this script generates two files:
- `<model>.pte` after calling `save_pte_program`
- `<model>.bp` after calling `save_bundled_program`

Since this example is intended to showcase the functionality of the bundled program, we shouldn't generate `<model>.pte` -- only `<model>.bp`.

We should also rename the function to reflect this.

Gasoonjia tarun292 do you agree w/ the above? Just a small thought I had while using this.

Reviewed By: tarun292, Gasoonjia

Differential Revision: D50069707

Author: Varun Puri

examples/sdk/scripts/export_bundled_program.py

@@ -16,7 +16,7 @@
 
 from ...models import MODEL_NAME_TO_MODEL
 from ...models.model_factory import EagerModelFactory
-from ...portable.utils import export_to_exec_prog, save_pte_program
+from ...portable.utils import export_to_exec_prog
 
 
 def save_bundled_program(
@@ -54,9 +54,8 @@ def save_bundled_program(
         file.write(bundled_program_buffer)
 
 
-def export_to_pte(model_name, model, method_names, example_inputs):
+def export_to_bundled_program(model_name, model, method_names, example_inputs):
     exec_prog = export_to_exec_prog(model, example_inputs)
-    save_pte_program(exec_prog.buffer, model_name)
 
     # Just as an example to show how multiple input sets can be bundled along, here we
     # create a list with the example_inputs tuple used twice. Each instance of example_inputs
@@ -91,4 +90,4 @@ def export_to_pte(model_name, model, method_names, example_inputs):
 
     method_names = ["forward"]
 
-    export_to_pte(args.model_name, model, method_names, example_inputs)
+    export_to_bundled_program(args.model_name, model, method_names, example_inputs)