Add zbf file export in 2.9

[tomflexcompute]

After discussion with tyler, momchil and all we think it might be worth it to officially add the zbf file export to our stable version in 2.9, even though we can't fully test it. At the same time we can add a warning like "this is an experimental feature, if you encounter any issues with the exported file, please contact us".

[lucas-flexcompute]

Sounds great, Tom, but I do not have the bandwidth to work on it. I'm more than happy to help whoever does the integration understand the code, though. It is super straightforward.
@tylerflex can you assign someone else to the issue?

[tylerflex]

I added @yaugenst-flex to re-assign as needed.

[lucas-flexcompute]

This is what I created when the request first came up: https://gist.github.com/lucas-flexcompute/ac8f8abc376f51222aad36beacb223ac

[bhnzhang]

Seems like the hard work has already been done by @lucas-flexcompute, is the task just to integrate his function into the frontend?

What would be a good way to interface with this function? I'm thinking it could be added to monitor objects so a user can call simdata['mon_name'].to_zbf()

[tylerflex]

Hi @bhnzhang , yes the task is just to integrate this into the frontend. Of course, if you spot anything that might need fixing, feel free to go for it too, but in principle this is just writing a wrapper for what Lucas already implemented.

I think adding a method to FieldData objects is the way to go. Might be worth seeing if any other monitor data could be exported but I don't think so.

A few things to think about while implementing

1. How can we test this function in the frontend without zemax?
2. If we can't fully test it, how can we effectively let the user know in case it doesn't work?
3. Are there any extra options to pass to to_zbf() that will be useful?