Refactor stack size handling in app.py for improved clarity

- Adjusted the placement of the fillna(1).astype(int) method for the stack_size column to ensure consistent data type handling and enhance clarity in the data processing logic.

app.py

@@ -158,8 +158,7 @@ with tab2:
             'own_percent_rank': dict(zip(st.session_state['ownership_df']['Player'], st.session_state['ownership_df']['Own'].rank(pct=True)))
         }
         # Create a copy of the dataframe for calculations
-        working_df = st.session_state['Contest'].copy() 
-        working_df['stack_size'] = working_df['stack_size'].fillna(1).astype(int)
+        working_df = st.session_state['Contest'].copy()
 
         if type_var == 'Classic':
             working_df['stack'] = working_df.apply(
@@ -226,7 +225,7 @@ with tab2:
             working_df['percentile_finish'] = working_df['index'].rank(pct=True)
             working_df['finish'] = working_df['index']
             working_df = working_df.drop(['sorted', 'index'], axis=1)
-            working_df['stack_size'] = working_df['stack_size'].fillna(1).astype(int)
+        working_df['stack_size'] = working_df['stack_size'].fillna(1).astype(int)
         st.session_state['field_player_frame'] = create_player_exposures(working_df, player_columns)
         st.session_state['field_stack_frame'] = create_stack_exposures(working_df)