Refactor contest data loading logic in app.py to improve session state checks

- Updated the logic for loading contest data to ensure the 'Load Contest Data' button only appears when 'Contest_file' is not already in session state, enhancing user experience and preventing redundant actions.
- Maintained existing checks for 'Adj_Contest' to ensure data integrity during the loading process.

app.py

@@ -72,9 +72,12 @@ with tab1:
             if 'Contest' in st.session_state:
                 del st.session_state['Contest']
         if parse_type == 'DB Search':
-            if st.button('Load Contest Data', key='load_contest_data'):
-                st.session_state['Contest_file'] = grab_contest_data('MLB', contest_name_var, contest_id_map, contest_date_map)
-                
+            if 'Contest_file' not in st.session_state:
+                if st.button('Load Contest Data', key='load_contest_data'):
+                    st.session_state['Contest_file'] = grab_contest_data('MLB', contest_name_var, contest_id_map, contest_date_map)
+            else:
+                pass
+
         if 'Contest_file' not in st.session_state and 'Adj_Contest' not in st.session_state:
             st.session_state['Contest'], st.session_state['ownership_df'], st.session_state['actual_df'], st.session_state['entry_list'] = load_contest_file(st.session_state['Contest_file'], sport_select)
             st.session_state['Contest'] = st.session_state['Contest'].dropna(how='all')