Allow for custom export file name

[salonee13]

Fixes #1417

What changes were proposed in this pull request?

Added functionality that allows the user to change the export file name to their own custom name if needed, if not, keeps it as the export path name

This shows the default export name:

This shows that it allows you to customize the export name to whatever you want:

This shows that the file exports and saves successfully with the custom export name:

How was this pull request tested?

Tested manually, see screenshots shown above. After the integration tests run, we will add a test to make sure this functionality works.

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

[elyra-bot]

Thanks for making a pull request to Elyra!

To try out this branch on binder, follow this link:

[kiersten-stokes]

This is looking really great!

Could we add some space beneath the export name field to bring it in like with how it looks in the submission dialog (shown below)?

[karlaspuldaro]

Thank you @salonee13 for implementing this enhancement, it looks great and works as expected :)
I only had one comment regarding the styling but everything else looks good to me!

For the integration test, you can add a new file (maybe call it pipelineexport.ts) to the integration tests folder.
One test case should be sufficient, and the workflow/commands would look something like:

1. create a runtime config
2. open a pipeline test file (helloworld.pipeline)
3. click export button
4. edit export name to something else
5. select the expected runtime config
6. press ok
7. check export name is in the succeeded dialog
8. press ok o the succeeded dialog
9. check the new file is listed in the file browser

[ptitzler]

Could you also change the order in which information is rendered and rename the label to Export Filename?

By moving the filename input to the bottom we group related information: the first inputs are specific to the runtime configuration that will be applied and the last three are specific to the exported file that will be produced:

• choose a file format
• choose a filename
• choose whether to overwrite the file if it already exists

[kiersten-stokes]

I'm approving as-is because we decided offline to add the above-mentioned integration test a follow-up issue/PR

Thank you so much, Salonee! I'll be getting a lot of use out of this feature