enhancement: use continue instead of break in nats fetch message loop

[atjhoendz]

Description

I found a memory leak issue in mage nats streaming pipeline, after I implemented it in production with more than 10 triggers of nats streaming pipeline.

I have fixed the memory issue by using "continue" instead of "break" in the NATS fetch message loop and updating the NATS close client method to wait for the result.

Before

1. Start the dev server
   

2. Turn on the trigger, 10 nats push subscriber
   

3. Test publish 10.000 messages
   

4. The mage-ai-app-1 was killed due to insufficient resources
   

5. The memory continues to grow, leading to the termination of mage-ai-server-1 due to insufficient resources.
   

After

1. Start the dev server
   

2. Turn on the trigger, 10 nats push subscriber
   

3. Test publish 10.000 messages
   

4. Memory usage is not as high as before
   
   

Need Help

Based on the data I've collected, I've noticed a significant spike in CPU usage during message processing, and I'm not sure why this is happening and need your help to investigate the cause of the high CPU usage.

How Has This Been Tested?

• Test publishing 10,000 messages. The pipeline code only prints NATS messages.

Checklist

• The PR is tagged with proper labels (bug, enhancement, feature, documentation)
• I have performed a self-review of my own code
• I have added unit tests that prove my fix is effective or that my feature works
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

cc:

[wangxiaoyou1993]

@atjhoendz do you want to make this PR ready for review so that we can merge it?

[atjhoendz]

@atjhoendz do you want to make this PR ready for review so that we can merge it?

Sorry I changed my mind, I think it would be better to investigate the high cpu usage first before merging.